TEST
Offline 109.122.200.58:28015 checked 16h 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 46% 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
- 17/ 100
- 283/ 400
- 184/ 225
- 132/ 100
- 388/ 1000
- 35/ 700
Quick answers
Tags and listings
Where does TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TEST: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
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): To join, your game has to be on protocol 2634; cs166652 (Build): The build number is 166652; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of TEST?
TEST does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 109.122.200.58:28015.
What's the uptime like for TEST?
TEST is down at the moment; it was last up 16 hours ago. The first sighting by Rust Going Deep was on 17 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 details
What schedule does TEST follow for wipes?
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. The world you are on now was created 46 hours.
Map and rules
What settings and rules have been applied to TEST?
The name of TEST contains no gather rate. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC is off: Valve's anti-cheat is not active.
Which map is active on TEST?
A procedural map, generated by the game, is in play on TEST.
Player count
What's the population like on TEST?
The last sighting of TEST was 16 hours ago; it is offline right now. The seven-day average is 1 players, with a peak of 1. The busiest point in the last 48 hours was 16:00 UTC, averaging 1 players.
What's TEST's rank among Rust servers?
Over the last seven days, TEST is #10,098 by player hours, among the top 46% of all ranked servers.
Getting in
What's the way to join TEST?
To join, open Rust, hit F1, and enter client.connect 109.122.200.58:28015. Or click Launch Rust on this page to open the game through Steam and connect.