A1180/ 200 players
Community#15,894
typical TESTING
Offline 15.204.83.240:21000 checked 1d ago
players now0of 40 slots
7-day average0peak –
rank#15,894top 72%
last wipe · restocked7d agono schedule published
next wipe · restock–no wipe seen yet
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestRankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A2106/ 200 players
A3261/ 275 players
B1120/ 200 players
B221/ 250 players
B3111/ 150 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
How should you read the tags on typical TESTING?
The server browser reads these tags that typical TESTING publishes: gmrust (Game mode): Rust survival, the standard way; mp40 (Max players): The cap is 40; ts8 (Group limit): The default cap is 8 per team; v2634 (Protocol): Protocol 2634: your game must match to get in; cs167398 (Build): Game build: 167398; ptrak (Networking): This is the standard RakNet layer the game uses; $r? (Region code): The region code is left blank. You will find its live player count, queue and world creation time in the tags too, displayed at the top here.
On Rust Vending Machine, which lists and filters can you find typical TESTING in?
These Rust Vending Machine lists include typical TESTING: Community Rust servers in stock. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules & map
What map is in play on typical TESTING?
The map on typical TESTING is procedural, size 1,000 with seed 1, generated by the game. You can view it on RustMaps from this page, since the same size and seed give the same map.
What rules does typical TESTING enforce, and what settings does it run?
No gather rate is given in the name of typical TESTING. 8 players is the default group size, and that is the cap here. You play survival, the usual game of gathering, building and raiding. You can fight and raid other players. In the server browser it is listed under Community, being a community server. VAC, Valve's anti-cheat, is enabled.
Server details
What location is typical TESTING in?
You will find no region published for typical TESTING. A server's stated location is what Rust Vending Machine shows; the actual machine location is not looked up. You can reach it at 15.204.83.240:21000.
What is the uptime like on typical TESTING?
No stock at present: typical TESTING is offline, last seen 32 hours ago. The uptime counter points to a restart about 2 days 3 hours ago. 58 of 144 hours online over the last 6 full days, or 40% uptime. It came to Rust Vending Machine's notice on 8 October 2026.
What is the performance like on typical TESTING?
Over the last 48 hours the average server fps was 240, with a low of 240. The entity count reached 4,319: that includes buildings, deployables and everything else. At most it drew 816 MB of memory. Lag, as players feel it, is low fps plus a growing entity count.
What Rust version does typical TESTING run?
Rust network protocol 2634 and build 167398 on Linux is what powers typical TESTING. To get in, your game must match the protocol; Steam keeps that updated.
Population
Where does typical TESTING sit in the rankings?
The last seven days of player hours place typical TESTING at #15,894, in the top 72% of all ranked servers.
How many players are on typical TESTING right now?
You will find typical TESTING offline right now; its last sighting was 32 hours ago. The past week gives an average of 0 players.
Wipe details
When does typical TESTING wipe?
Too few wipes of typical TESTING are recorded to tell what its rhythm is. On Thursday 5 November at 19:00 UTC the monthly force wipe comes, and every Rust server wipes. 7 days 23 hours ago it made the world it is using now.
Join the server
What steps do you take to join typical TESTING?
Open Rust and press F1 for the console, then type client.connect 15.204.83.240:21000. Or use the Launch Rust button here to open the game through Steam and connect.
Server tags
what each one meansPublished as mp40,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game mode Rust survival, the standard way.
mp40
Max players The cap is 40.
ts8
Group limit The default cap is 8 per team.
v2634
Protocol Protocol 2634: your game must match to get in.
cs167398
Build Game build: 167398.
ptrak
Networking This is the standard RakNet layer the game uses.
$r?
Region code The region code is left blank.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.