Offline 109.38.151.222:28215 checked 39d ago
Wipeborn RustNav tier2
Connect
srv = rust.server("109.38.151.222:28217")
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 bestWipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 | Sat 19 Sep, 20:22 UTC40d ago | 0 | NaN | running | 0 |
| 1 | Sat 19 Sep, 10:30 UTC40d ago | 0 | NaN | 0.4 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 109.38.151.222:28215
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Sep 2026, 20:22 UTC
- hostname
- –
- first seen
- 18 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 · 150 on average | 68/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 115/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 38/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 124/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 346/350 |
Quick answers
From the figures on this page.
Population
What position does Wipeborn RustNav tier2 take in the server rankings?
Over the last seven days Wipeborn RustNav tier2 sits at #15,481 on player hours, in the top – of ranked servers.
How full does Wipeborn RustNav tier2 run?
The current row shows Wipeborn RustNav tier2 offline; the last response was 39 days 11 hours ago.
Server facts
What Rust version does Wipeborn RustNav tier2 run?
Version Rust network protocol 2633 and build 164530 on Linux is reported by Wipeborn RustNav tier2. Steam updates your game for you, but the protocol must match to join.
How reliable is Wipeborn RustNav tier2, and is it up?
Wipeborn RustNav tier2 is offline at this refresh; the last response came 39 days 11 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 18 September 2026.
Which location does Wipeborn RustNav tier2 run from?
For Wipeborn RustNav tier2, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 109.38.151.222:28215.
Map and rules
What rules and settings are recorded for Wipeborn RustNav tier2?
You will not find a gather rate in the string Wipeborn RustNav tier2. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
Which map has Wipeborn RustNav tier2 loaded?
The game generates its map: procedural, on Wipeborn RustNav tier2.
Wipes and dates
On what schedule does Wipeborn RustNav tier2 wipe?
Too few wipes are on record for Wipeborn RustNav tier2 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 40 days ago.
On Wipeborn RustNav tier2, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which Rust Data filters and lists contain Wipeborn RustNav tier2?
These Rust Data lists include Wipeborn RustNav tier2: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Wipeborn RustNav tier2 hold?
The game's server browser reads these tags from Wipeborn RustNav tier2: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): The server lists 8 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Wipeborn RustNav tier2?
In Rust, F1 opens the console: type client.connect 109.38.151.222:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.