TEST
Offline 92.208.31.149:28015 checked 22d 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 71% 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, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 24 Sep, 12:53 UTC23d 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
- 139/ 200
- 302/ 300
- 242/ 275
- 781/ 800
- 104/ 200
- 104/ 250
Quick answers
Tags and filters
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?
The server browser shows these tags for TEST: gmrust (Game mode): This is the standard Rust survival experience; mp2 (Max players): It holds 2 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): It's on build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is TEST in?
There is no published region for TEST. 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 92.208.31.149:28015.
What's the uptime like for TEST?
Right now TEST is offline, having last been seen 22 days 8 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 24 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. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does TEST wipe?
Too few wipes are on record for TEST 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. 23 days 14 hours is how long ago this world came into being.
What happens on wipe day at TEST?
Recent wipes have averaged a busiest crowd of 1 players. The peak crowd on the latest wipe came 1 hours in.
Rules and settings
What settings and rules have been applied to TEST?
No gather rate appears in the name of TEST. 8 players is the group cap, the game's default. It runs survival, 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?
TEST uses a game-generated procedural map.
Player stats
Is TEST busy?
Right now TEST is offline, with its last appearance 22 days 8 hours ago.
What position does TEST hold in the server rankings?
For player hours in the last seven days, TEST ranks #16,487, within the top 71% of ranked servers.
Getting in
What's the way to join TEST?
To join, open Rust, hit F1, and enter client.connect 92.208.31.149:28015. Or click Launch Rust on this page to open the game through Steam and connect.