TEST
Offline 194.33.85.234: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 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 filters
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?
TEST's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): There are 10 slots on this server; 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; cs164530 (Build): It's on build 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Where can you find 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 194.33.85.234:28015.
What's the uptime like for TEST?
The server TEST is not reachable at the moment; the last sighting was 21 days 17 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 26 September 2026.
What is the Rust version for TEST?
The version on TEST is Rust network protocol 2633 and build 164530, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
What schedule does TEST follow for wipes?
TEST's rhythm is unclear because not enough wipes are on record yet. 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 28 days 15 hours ago.
Map and rules
What settings and rules have been applied to TEST?
No gather rate appears in the name of TEST. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
What's the map on TEST?
The map on TEST is procedural, made by the game.
Player count
Is TEST busy?
The last sighting of TEST was 21 days 17 hours ago; it is offline right now.
Where does TEST sit in the rankings?
Over the last seven days, TEST is #16,789 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 194.33.85.234:28015. Alternatively, click Launch Rust on this page to join via Steam.