Offline 91.122.255.48:22015 checked 24d ago
RustOfWar#2 Test
Connect
srv = rust.server("91.122.255.48:22017")
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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 3 Oct, 11:29 UTC24d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 91.122.255.48:22015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:29 UTC
- hostname
- –
- first seen
- 2 Oct 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 · 157 on average | 93/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 94/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 37/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 | 15/1000 |
Quick answers
From the figures on this page.
Population
How does RustOfWar#2 Test compare in the rankings?
Over the last seven days RustOfWar#2 Test sits at #16,006 on player hours, in the top 70% of ranked servers.
What population does RustOfWar#2 Test carry?
RustOfWar#2 Test returns no live count at this refresh, having last been seen 24 days 18 hours ago.
About the server
What Rust version does RustOfWar#2 Test run?
The build is Rust network protocol 2634 and build 166652 on Windows, run by RustOfWar#2 Test. Steam updates your game for you, but the protocol must match to join.
Is RustOfWar#2 Test up, and what does its uptime show?
The latest sample has RustOfWar#2 Test offline, with a last sighting 24 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 2 October 2026.
In which location is RustOfWar#2 Test hosted?
There is no region published for RustOfWar#2 Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 91.122.255.48:22015.
Settings and map
Which settings and rules does RustOfWar#2 Test run?
No gather rate appears in the name: RustOfWar#2 Test. Eight players per group: that is the game's default, and it applies here. 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 is running: Valve's anti-cheat is on.
Wipe data
When does RustOfWar#2 Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of RustOfWar#2 Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 24 days 19 hours ago, and that is the one in play.
What is wipe day on RustOfWar#2 Test like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold RustOfWar#2 Test, and which filters?
These Rust Data lists include RustOfWar#2 Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on RustOfWar#2 Test hold?
Read by the game's server browser, the tags RustOfWar#2 Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join RustOfWar#2 Test?
In Rust, F1 opens the console: type client.connect 91.122.255.48:22015. Launch Rust on this page does the same by opening the game through Steam and connecting.