Test Server
Offline 23.81.34.199:28015 checked 26d 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 67% 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
- 244/ 400
- 180/ 225
- 133/ 100
- 290/ 1000
- 22/ 700
Quick answers
Tags and listings
Where does Test Server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Test Server: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on Test Server?
gmrust (Game mode): This is the standard Rust survival experience; mp30 (Max players): The slot count is 30; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): It's on build 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): Carbon is the plugin framework it uses — that is the tag list Test Server puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of Test Server?
There is no published region for Test Server. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 23.81.34.199:28015.
What's the uptime like for Test Server?
The server Test Server is not reachable at the moment; the last sighting was 26 days 12 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 21 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Test Server?
Rust network protocol 2633 and build 164530 is what Test Server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does Test Server wipe?
Too few wipes are on record for Test Server to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 26 days 13 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Test Server running?
Its name does not state a gather rate for Test Server. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Carbon. The server runs Valve's anti-cheat, VAC.
Which map is active on Test Server?
Test Server uses a game-generated procedural map.
Player stats
Is Test Server busy?
Right now Test Server is offline, with its last appearance 26 days 12 hours ago.
Where does Test Server sit in the rankings?
For player hours in the last seven days, Test Server ranks #15,471, within the top 67% of ranked servers.
How to join
What's the way to join Test Server?
To join, open Rust, hit F1, and enter client.connect 23.81.34.199:28015. Or click Launch Rust on this page to open the game through Steam and connect.