Test Server
Offline 86.145.193.239:28015 checked 34d 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 bestWipe 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
- 841/ 100
- 114/ 400
- 106/ 245
- 128/ 100
- 273/ 1000
- 19/ 700
Quick answers
Tags and filters
Where does Test Server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Test Server: Modded Rust servers. The server list shows it under 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): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163794 (Build): It's on build 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): This server relies on Carbon for plugins — that is the tag list Test Server puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What's the location of Test Server?
There is no published region for Test Server. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 86.145.193.239:28015.
What's the uptime like for Test Server?
Right now Test Server is offline, having last been seen 34 days 5 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 13 September 2026.
What is the Rust version for Test Server?
Rust network protocol 2633 and build 163794 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
What schedule does Test Server follow for wipes?
Test Server'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 34 days 5 hours.
Rules and settings
What settings and rules have been applied to Test Server?
Its name does not state a gather rate for Test Server. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Carbon plugins are running here. VAC, Valve's anti-cheat, is enabled.
What's the map on Test Server?
Test Server uses a game-generated procedural map.
Player stats
How many players are on Test Server?
The last sighting of Test Server was 34 days 5 hours ago; it is offline right now.
What position does Test Server hold in the server rankings?
For player hours in the last seven days, Test Server ranks #13,043, within the top – of ranked servers.
How to join
How do you get into Test Server?
Open Rust and press F1, then type client.connect 86.145.193.239:28015. Alternatively, click Launch Rust on this page to join via Steam.