Test Server
Offline 109.252.100.52: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 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
- 17/ 100
- 244/ 400
- 180/ 225
- 133/ 100
- 290/ 1000
- 22/ 700
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: Modded ^z and Carbon ^y; Group limit: 5 or more.
What's the meaning of the tags on Test Server?
Test Server's game browser tags read: 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): To join, your game has to be on protocol 2633; cs164530 (Build): It's on build 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): This server relies on Carbon for plugins. 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?
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. You can reach it at 109.252.100.52:28015.
What's the uptime like for Test Server?
Right now Test Server is offline, having last been seen 26 days 13 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 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
What schedule does Test Server follow for wipes?
Test Server's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 26 days 16 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to Test Server?
The name of Test Server 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. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. You will find Carbon plugins installed. VAC is on: Valve's anti-cheat is active.
What's the map on Test Server?
Test Server uses a game-generated procedural map.
Player stats
How many players are on Test Server?
Right now Test Server is offline, with its last appearance 26 days 13 hours ago.
What position does Test Server hold in the server rankings?
For player hours in the last seven days, Test Server ranks #13,238, within the top 58% of ranked servers.
Getting in
What's the process to join Test Server?
To join, open Rust, hit F1, and enter client.connect 109.252.100.52:28015. Or click Launch Rust on this page to open the game through Steam and connect.