TEST
Offline 92.208.8.76:28015 checked 13d 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 61% 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
- 1000/ 100
- 231/ 400
- 211/ 245
- 127/ 100
- 491/ 1000
- 43/ 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. 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?
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; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166586 (Build): It's on build 166586; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^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. 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. You can reach it at 92.208.8.76:28015.
What's the uptime like for TEST?
Right now TEST is offline, having last been seen 13 days 22 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 3 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 info
What schedule does TEST follow for wipes?
Too few wipes are on record for TEST to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 15 days 4 hours is how long ago this world came into being.
Rules and settings
What settings are in place on TEST?
Its name does not state a gather rate for TEST. Up to 8 players per group, which is the default. 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. Plugins in use: Oxide. The server does not run Valve's anti-cheat, VAC.
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?
The last sighting of TEST was 13 days 22 hours ago; it is offline right now.
What's TEST's rank among Rust servers?
For player hours in the last seven days, TEST ranks #13,901, within the top 61% of ranked servers.
Getting in
How do you get into TEST?
To join, open Rust, hit F1, and enter client.connect 92.208.8.76:28015. Or click Launch Rust on this page to open the game through Steam and connect.