Test
Offline 1.170.144.253:28015 checked 14d 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 64% 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
- 304/ 400
- 183/ 225
- 121/ 100
- 390/ 1000
- 31/ 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 Oxide ^o; 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; mp5 (Max players): There are 5 slots on this server; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166586 (Build): This server runs build 166586; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. 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. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 1.170.144.253:28015.
What's the uptime like for Test?
The server Test is not reachable at the moment; the last sighting was 14 days 3 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 3 October 2026.
What is the Rust version for Test?
The version on Test is Rust network protocol 2634 and build 166586, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Test wipe?
The wipes recorded for Test are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 16 days 2 hours.
Settings and map
What settings are in place on Test?
The name of Test contains no gather rate. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
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 14 days 3 hours ago and is offline as you read this.
Where does Test sit in the rankings?
For player hours in the last seven days, Test ranks #14,424, within the top 64% of ranked servers.
Getting in
How do you get into Test?
To join, open Rust, hit F1, and enter client.connect 1.170.144.253:28015. Or click Launch Rust on this page to open the game through Steam and connect.