Station XX-10334 · no signal
[NotPublic] Test branch
Offline 84.21.165.111:28015 checked 12h ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #10,334
- top 46%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 14h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M0.0■steady+0 players
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 46% 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 7d 14h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 7d 14hThu 5 Nov, 19:00 UTCFW
- 35d 14hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 20:48 UTC FW27d ago | M0.0■steady | 1 | – | running | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [NotPublic] Test branch?
[NotPublic] Test branch uses a procedural map, which the game generates.
Which settings and rules apply on [NotPublic] Test branch?
No gather rate appears in the name of [NotPublic] Test branch. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on [NotPublic] Test branch right now?
No players are recorded on [NotPublic] Test branch at this moment; it is offline, and the last sighting was 12 hours ago. Across seven days this server recorded an average of 0 players and a peak of 1.
How does [NotPublic] Test branch rank against other Rust servers?
Over the last seven days, [NotPublic] Test branch recorded enough player hours to reach #10,334 worldwide, placing it in the top 46% of all ranked servers.
Operator and location
How reliably does [NotPublic] Test branch stay online?
[NotPublic] Test branch is down at the moment; the last recorded contact was 12 hours ago. 18 of 168 hours in the last 7 full days were up time, 11% of the total. On 15 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is [NotPublic] Test branch hosted?
Nothing about a region comes from [NotPublic] Test branch. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 84.21.165.111:28015.
What build of Rust does [NotPublic] Test branch use?
[NotPublic] Test branch is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on [NotPublic] Test branch?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does [NotPublic] Test branch run its wipes?
Once a month [NotPublic] Test branch wipes, at the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 27 days 10 hours.
Lists and tags
What do the server tags on [NotPublic] Test branch mean?
These are the tags [NotPublic] Test branch publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp5 (Max players): 5 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; jp0 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [NotPublic] Test branch appear?
These Rust Server Trends lists include [NotPublic] Test branch: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto [NotPublic] Test branch?
Enter client.connect 84.21.165.111:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.