Test Server
Offline 212.3.136.165:27015 checked 27d 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 58% 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
- 144/ 2000
- 254/ 2000
- 51/ 200
- 53/ 250
- 47/ 200
- 68/ 200
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 and Go deep on PvE servers. Its entry appears under the filters Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Test Server?
Test Server's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp50 (Max players): There are 50 slots on this server; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163794 (Build): The build number is 163794; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^p (PvE): No PvP here: the danger comes from the environment; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What location is Test Server in?
Test Server does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 212.3.136.165:27015.
How reliable is Test Server?
Test Server is down at the moment; it was last up 27 days 3 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 14 September 2026.
What Rust version is Test Server on?
On Windows, Test Server runs Rust network protocol 2633 and build 163794. 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. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 34 days 8 hours is how long ago this world came into being.
Settings and map
What settings are in place on Test Server?
The name of Test Server contains no gather rate. 8 players is the group cap, the game's default. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on Test Server?
A procedural map, generated by the game, is in play on Test Server.
Player stats
Is Test Server busy?
Right now Test Server is offline, with its last appearance 27 days 3 hours ago.
What's Test Server's rank among Rust servers?
Over the last seven days, Test Server is #13,297 by player hours, among the top 58% of all ranked servers.
How to join
How do you get into Test Server?
Open Rust and press F1, then type client.connect 212.3.136.165:27015. Alternatively, click Launch Rust on this page to join via Steam.