test
Offline 146.52.43.181:28015 checked 20d 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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 27 Sep, 21:41 UTC20d ago | 1 | – | running | 0 |
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
- 327/ 400
- 527/ 600
- 199/ 225
- 275/ 325
- 285/ 350
- 348/ 425
Quick answers
Tags and listings
Where does test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include test: Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on test?
gmrust (Game mode): Survival, as standard Rust does it; mp500 (Max players): The slot count is 500; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code — that is the tag list test 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 location is test in?
test does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 146.52.43.181:28015.
How reliable is test?
Right now test is offline, having last been seen 20 days ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 27 September 2026 is when Rust Going Deep first saw it.
What Rust version is test on?
The version on test is Rust network protocol 2633 and build 165217, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
How often 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 20 days.
What happens on wipe day at test?
Across its recent wipes, the average busiest point drew 1 players. On the latest wipe, 0 hours passed before the crowd peaked.
Map and rules
Which rules and settings is test running?
The name of test contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. Community is where the server browser puts it, as a community server. VAC is on: Valve's anti-cheat is active.
Which map is active on test?
A procedural map, generated by the game, is in play on test.
Player stats
What's the population like on test?
test was last seen 20 days ago and is offline as you read this.
What position does test hold in the server rankings?
Over the last seven days, test is #15,903 by player hours, among the top 67% of all ranked servers.
Getting in
What's the way to join test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 146.52.43.181:28015.