test
Offline 5.164.252.134:28015 checked 19d 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 68% 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
- 20/ 100
- 137/ 400
- 94/ 225
- 128/ 100
- 123/ 1000
- 5/ 700
Quick answers
Tags and filters
Where does test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include test: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What's the meaning of the tags on test?
gmrust (Game mode): Survival, as standard Rust does it; mp15 (Max players): There are 15 slots on this server; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166016 (Build): The build number is 166016; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): This server relies on Carbon for plugins — that is the tag list test puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
Where can you find test?
test 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. To connect, use 5.164.252.134:28015.
What's the uptime like for test?
test is down at the moment; it was last up 19 days 16 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 28 September 2026.
What Rust version is test on?
The version on test is Rust network protocol 2634 and build 166016, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
When does test wipe?
The wipes recorded for test are too few to reveal its rhythm. 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 19 days 17 hours.
Settings and map
What settings and rules have been applied to test?
The name of test contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Carbon plugins are running here. VAC, Valve's anti-cheat, is enabled.
Which map is active on test?
The map on test is procedural, made by the game.
Player count
Is test busy?
test was last seen 19 days 16 hours ago and is offline as you read this.
Where does test sit in the rankings?
Over the last seven days, test is #16,247 by player hours, among the top 68% of all ranked servers.
How to join
How do you get into test?
Open Rust and press F1, then type client.connect 5.164.252.134:28015. Alternatively, click Launch Rust on this page to join via Steam.