TEST
Offline 109.122.200.78:28015 checked 14d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 65% 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 6/ 100
- 85/ 400
- 46/ 245
- 121/ 100
- 129/ 1000
- 14/ 700
Quick answers
Tags and listings
Where does TEST appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TEST are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TEST?
The server browser shows these tags for TEST: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166652 (Build): It's on build 166652; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is TEST in?
No region comes from TEST. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 109.122.200.78:28015.
Is TEST up, and how often does it stay online?
TEST is down at the moment; it was last up 14 days 8 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 3 October 2026.
What is the Rust version for TEST?
Rust network protocol 2634 and build 166652 is what TEST runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does TEST wipe?
TEST's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 14 days 12 hours ago.
Rules and settings
Which rules and settings is TEST running?
No gather rate appears in the name of TEST. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
What's the map on TEST?
The map on TEST is procedural, made by the game.
Population
Is TEST busy?
Right now TEST is offline, with its last appearance 14 days 8 hours ago.
What position does TEST hold in the server rankings?
For player hours in the last seven days, TEST ranks #14,747, within the top 65% of ranked servers.
Getting in
What's the process to join TEST?
Open Rust and press F1, then type client.connect 109.122.200.78:28015. Alternatively, click Launch Rust on this page to join via Steam.