TEST
Offline 188.241.241.122:28015 checked 24d 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 60% 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 search
Where does TEST appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TEST are: 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; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs164530 (Build): The build number is 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — 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.
About the server
What location is TEST in?
TEST does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 188.241.241.122:28015.
What's the uptime like for TEST?
TEST is down at the moment; it was last up 24 days 22 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 20 September 2026.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 is what TEST runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
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. 28 days 16 hours is how long ago this world came into being.
Map and rules
What settings and rules have been applied to TEST?
Its name does not state a gather rate for TEST. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on TEST?
A procedural map, generated by the game, is in play on TEST.
Population
What's the population like on TEST?
Right now TEST is offline, with its last appearance 24 days 22 hours ago.
Where does TEST sit in the rankings?
For player hours in the last seven days, TEST ranks #13,204, within the top 60% of ranked servers.
How to join
What's the way to join TEST?
To join, open Rust, hit F1, and enter client.connect 188.241.241.122:28015. Or click Launch Rust on this page to open the game through Steam and connect.