TEST
Key statistics
the figures behind the quote- Players now
- 2/ 5 40% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #12,625 no region published
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 27d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 2 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 16 Sep 2026 no hostname published
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 bestWipe schedule
too few wipes seen yet- wipe-day peak
- 2 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 16 Sep, 15:53 UTC27d ago | 2 | – | running | 0 |
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 42/245 | ▲+16+62.1% | |
| 2 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 90/100 | ▪+0−0.2% | |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 15/1000 | ▼−8−33.5% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 5/1000 | ▼−6−53.0% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average | 21/700 | ▼−50−70.5% | |
| 6 | SURVIVORS.GG | 2 x Vanilla | Monthlygroups of 30+ · monthly · 72 on average | 23/200 | ▲+3+17.7% |
Quick answers
from the figures on this pageRules & Settings
How is TEST configured in terms of rules and settings?
The name of TEST carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are running. VAC is active.
What is the current map on TEST?
TEST uses a procedural map, which the game generates.
Player Count
Where does TEST sit in the rankings?
In the top – of all ranked servers, TEST is #12,625 on player hours over the last seven days.
How many players does TEST have?
At present, TEST is offline; the last sighting was 27 days 7 hours ago.
Wipe Frequency
What happens on wipe day at TEST?
Recent wipes at this server drew an average peak of 2 players. 1 hours after the latest wipe, the crowd reached its peak.
On what cycle does TEST wipe?
There are too few wipes on record for TEST to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 27 days 7 hours old.
Server Info
What is the location of TEST?
For TEST, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 94.232.204.213:28015 is its address.
What Rust version is TEST running?
The version in use at TEST: Rust network protocol 2633 and build 163794, on Windows. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of TEST?
No response from TEST. It was last seen 27 days 7 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. 16 September 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on TEST?
These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp5 (Max players): Capacity: 5 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): To join, your game needs protocol 2633; cs163794 (Build): Game build: 163794; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does TEST show up in Rust Analytics lists and filters?
These Rust Analytics lists include TEST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Joining the Server
What steps do I take to join TEST?
The console route: start Rust, press F1, enter client.connect 94.232.204.213:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp5,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
mp5
ts8
v2633
cs163794
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.