Offline 45.66.162.55:28015 checked 15d ago
[NotPublic] Test branch
Connect
srv = rust.server("45.66.162.55:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 13h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 13h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 13h | 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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:14 UTC FW26d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 45.66.162.55:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:07 UTC
- hostname
- –
- first seen
- 24 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 158 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 59/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 8/1000 |
Quick answers
From the figures on this page.
Population data
What position does [NotPublic] Test branch take in the server rankings?
Rank #14,496 on seven-day player hours for [NotPublic] Test branch, within the top 66% of all ranked servers.
What population does [NotPublic] Test branch carry?
The current row shows [NotPublic] Test branch offline; the last response was 15 days 11 hours ago.
Server data
What is the Rust version on [NotPublic] Test branch?
The build is Rust network protocol 2634 and build 167398 on Windows, run by [NotPublic] Test branch. The protocol has to match before you can join, and Steam does the updating.
Is [NotPublic] Test branch up, and what does its uptime show?
[NotPublic] Test branch is offline at this refresh; the last response came 15 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 24 September 2026.
Which location does [NotPublic] Test branch run from?
For [NotPublic] Test branch, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 45.66.162.55:28015 is its address.
Settings and map
What rules and settings are recorded for [NotPublic] Test branch?
No gather rate appears in the name: [NotPublic] Test branch. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has [NotPublic] Test branch loaded?
A procedural map runs on [NotPublic] Test branch, generated by the game.
Wipes and dates
When does [NotPublic] Test branch wipe, and on what schedule?
A single wipe each month, the force wipe, is all [NotPublic] Test branch does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 26 days 11 hours ago.
On [NotPublic] Test branch, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain [NotPublic] Test branch?
These Rust Data lists include [NotPublic] Test branch: 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.
How should you read the server tags on [NotPublic] Test branch?
Read by the game's server browser, the tags [NotPublic] Test branch publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; jp0 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join [NotPublic] Test branch?
In Rust, F1 opens the console: type client.connect 45.66.162.55:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.