Test Server
Offline 187.121.95.171:28015 checked 4d 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Tuesday 20 October, 14:38 UTC, in 2d 5h. Weekly: 7 days after its last 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
Quick answers
Tags and filters
Where does Test Server appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Test Server are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.
How should you read the tags on Test Server?
Test Server's game browser tags read: gmvanilla (Game mode): Vanilla survival gameplay; mp100 (Max players): There are 100 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): The build number is 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^w (Weekly): A wipe every week; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Where can you find Test Server?
There is no published region for Test Server. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 187.121.95.171:28015.
Is Test Server up, and how often does it stay online?
Test Server is down at the moment; it was last up 4 days 18 hours ago. It was up 0% of the time over the last full 4 days, 0 of 96 hours. Rust Going Deep has had it on record since 13 October 2026.
What is the Rust version for Test Server?
On Windows, Test Server runs Rust network protocol 2634 and build 167781. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
How often does Test Server wipe?
The next wipe for Test Server is an estimate based on weekly: 7 days after its last wipe. Tuesday 20 October at 14:38 UTC is when the next wipe is due. 4 days 18 hours is how long ago this world came into being. The tags show wipes set to happen every week.
Settings and map
Which rules and settings is Test Server running?
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. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. The server runs Valve's anti-cheat, VAC.
What's the map on Test Server?
A procedural map, generated by the game, is in play on Test Server.
Population
Is Test Server busy?
Test Server was last seen 4 days 18 hours ago and is offline as you read this. Across the last seven days, the typical count has been 0 players.
What's Test Server's rank among Rust servers?
For player hours in the last seven days, Test Server ranks #15,843, within the top 72% of ranked servers.
Getting in
What's the process to join Test Server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 187.121.95.171:28015.