Station XX-14496 · no signal
[NotPublic] Test branch
Offline 45.66.162.55:28015 checked 15d ago
- Players now
- 1/ 5
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,496
- top 66%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 8d 6h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 5 slots
- Motion · 24 h
- M –not enough readings
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 66% 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 8d 6h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 8d 6hThu 5 Nov, 19:00 UTCFW
- 36d 6hThu 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 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 19:14 UTC FW26d ago | M0.0■steady | 0 | – | running | 0 |
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 pageServer rules
Which map is running on [NotPublic] Test branch?
A procedural map runs on [NotPublic] Test branch, generated by the game.
Which settings and rules apply on [NotPublic] Test branch?
No gather rate appears in the name of [NotPublic] Test branch. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on [NotPublic] Test branch?
A reading taken now finds [NotPublic] Test branch offline; the most recent activity was 15 days 18 hours ago.
How does [NotPublic] Test branch rank against other Rust servers?
Over the last seven days, [NotPublic] Test branch recorded enough player hours to reach #14,496 worldwide, placing it in the top 66% of all ranked servers.
Server facts
How reliably does [NotPublic] Test branch stay online?
No contact with [NotPublic] Test branch right now, and the last recorded contact was 15 days 18 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 24 September 2026 is when Rust Server Trends first recorded it.
Which region does [NotPublic] Test branch run from?
Nothing about a region comes from [NotPublic] Test branch. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 45.66.162.55:28015 is the address it uses.
Which Rust version is [NotPublic] Test branch running?
Rust network protocol 2634 and build 167398 on Windows is what [NotPublic] Test branch runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on [NotPublic] Test branch?
0 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
How often does [NotPublic] Test branch wipe, and on which days?
At the force wipe each month [NotPublic] Test branch wipes, and at no other time. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 26 days 18 hours.
Server tags
What do the server tags on [NotPublic] Test branch mean?
Tags published by [NotPublic] Test branch and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; jp0 (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. 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.
Connecting
What steps get you onto [NotPublic] Test branch?
To join, enter client.connect 45.66.162.55:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.