Test
Offline 193.141.60.250:47821 checked 8d 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 72% 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
- 289/ 400
- 172/ 225
- 132/ 100
- 354/ 1000
- 27/ 700
Quick answers
Tags and listings
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; Last wipe: In the last 2 weeks.
How should you read the tags on Test?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): There are 2 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166586 (Build): The build number is 166586; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Test puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What's the location of Test?
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. You can reach it at 193.141.60.250:47821.
What's the uptime like for Test?
Right now Test is offline, having last been seen 8 days 11 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 9 October 2026.
What Rust version is Test on?
On Windows, Test runs Rust network protocol 2634 and build 166586. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does Test follow for wipes?
Test's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 8 days 11 hours is how long ago this world came into being.
Map and rules
Which rules and settings is Test running?
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. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
What's the map on Test?
The map on Test is procedural, made by the game.
Player stats
Is Test busy?
Test was last seen 8 days 11 hours ago and is offline as you read this.
Where does Test sit in the rankings?
Over the last seven days, Test is #15,842 by player hours, among the top 72% of all ranked servers.
Getting in
How do you get into Test?
Open Rust and press F1, then type client.connect 193.141.60.250:47821. Alternatively, click Launch Rust on this page to join via Steam.