TEST
Offline 31.7.57.58:28015 checked 21d 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
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
- 1001/ 100
- 82/ 400
- 43/ 245
- 120/ 100
- 124/ 1000
- 13/ 700
Quick answers
Tags and search
Where does TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TEST: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TEST?
TEST's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
Where can you find TEST?
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 31.7.57.58:28015.
Is TEST up, and how often does it stay online?
TEST is down at the moment; it was last up 21 days 3 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 26 September 2026.
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 info
What schedule does TEST follow for wipes?
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. This world has been running since 21 days 4 hours ago.
Map and rules
Which rules and settings is TEST running?
No gather rate appears in the name of TEST. 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. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
What's the map on TEST?
TEST uses a game-generated procedural map.
Player stats
Is TEST busy?
TEST was last seen 21 days 3 hours ago and is offline as you read this.
What's TEST's rank among Rust servers?
Over the last seven days, TEST is #15,780 by player hours, among the top 67% of all ranked servers.
Join info
What's the process to join TEST?
Open Rust and press F1, then type client.connect 31.7.57.58:28015. Alternatively, click Launch Rust on this page to join via Steam.