TEST
Offline 185.207.214.198:35400 checked 26d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 17h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 34d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 20:16 UTC26d ago | 0 | – | running | 0 |
| Thu 1 Oct, 17:58 UTC FW28d ago | 8 | – | 2.1 days | 3 |
| Tue 29 Sep, 16:28 UTC30d ago | 8 | held half | 2.1 days | 1 |
| Mon 28 Sep, 19:35 UTC31d ago | 3 | – | 0.9 days | 0 |
| Sun 27 Sep, 17:51 UTC32d ago | 2 | – | 1.1 days | 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 | Profile | Players now |
|---|---|---|
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 8 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 38 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 7 / 1000 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 79 on average | 24 / 1000 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 76 on average | 33 / 1000 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 73 on average | 76 / 1000 |
Quick answers
from the figures on this pageWipe cycle
On what cycle does TEST wipe?
With the force wipe, once a month, TEST wipes. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 26 days 5 hours ago the current world was made. The tags carry a monthly wipe schedule.
Wipe day on TEST: what should you expect?
Recent wipes averaged a busiest count of 5 players. 0 hours after the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server details
What is the hosting location of TEST?
No region is published by TEST. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 185.207.214.198:35400 is its address.
What Rust build does TEST run?
Rust network protocol 2634 and build 166652 on Windows is the setup for TEST. Joining requires the same protocol on your game; Steam handles the update.
Is TEST up, and how steady is its uptime?
Last seen 26 days 5 hours ago, TEST now reports offline. Of 168 hours in the last 7 full days, 0 were up: 0%. 13 September 2026 is when Rust Server Analytics first recorded it.
Tags
How should the tags on TEST be read?
The game's server browser reads the tags TEST publishes: gmvanilla (Game mode): Vanilla ruleset survival; mp200 (Max players): Player slots: 200; ts10 (Group limit): Team size is capped at 10; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166652 (Build): The game build is 166652; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does TEST appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists TEST fits are: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Population
What position does TEST hold in the server rankings?
On player hours over seven days, TEST ranks #15,998, within the top 70% of ranked servers.
What is the population of TEST?
No response from TEST at the latest check, with a last sighting 26 days 5 hours ago.
Settings
What are the settings on TEST, and its rules?
Gather rate is not mentioned in the name of TEST. A maximum of 10 players per group applies. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Modded category lists it; plugins or settings change the game. The plugin framework is Oxide. Anti-cheat status: VAC on.
What is the map for TEST?
TEST uses a procedural map of size 4,500 with seed 1752400757, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here. Named map: Custom Map.
How to join
How can a player join TEST?
In the Rust console (F1), enter client.connect 185.207.214.198:35400. Launch Rust on this page also works, opening Rust through Steam and connecting you.