Online 139.99.142.169:23251 checked 13m ago
Solo War
Connect
srv = rust.server("139.99.142.169:23252")
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, measured since 27 Oct. 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 23% 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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 06:49 UTC1d ago | NaN | 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
4000 · seed 1410201025
- map
- Procedural Map
- size
- 4000
- seed
- 1410201025
Server
srv.info()- address
- 139.99.142.169:23251
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 06:49 UTC
- hostname
- –
- first seen
- 27 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 · 151 on average | 153/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 194/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 97/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 221/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
What position does Solo War take in the server rankings?
Rank #5,155 on seven-day player hours for Solo War, within the top 23% of all ranked servers.
How many players does Solo War hold at once?
Current row: 0 players on Solo War, against 10 slots. Over the last seven days it averaged 1 players and peaked at 3. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 3 players.
Server data
How well does Solo War perform?
The 48-hour average is 173 server fps, with a low of 115. The entity count peaked at 93,985, covering buildings, deployables and the rest of the world. The memory field tops out at 3,941 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Solo War on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Solo War. The protocol has to match before you can join, and Steam does the updating.
How reliable is Solo War, and is it online now?
Solo War reports itself online at the current refresh. A restart about 13 hours ago is what its reported uptime implies. 15 of 24 hours up over the last 1 full day, or 62%. Rust Data logged it first on 27 October 2026.
In which location is Solo War hosted?
For Solo War, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 139.99.142.169:23251 is its address.
Map and rules
What rules and settings are recorded for Solo War?
No gather rate appears in the name: Solo War. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Solo War selected?
Size 4,000, seed 1410201025: the procedural map on Solo War, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Solo War wipe, and on what schedule?
Too few wipes are on record for Solo War 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. A new world was started 34 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold Solo War, and which filters?
The Rust Data lists that Solo War fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on Solo War?
Read by the game's server browser, the tags Solo War publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Solo War?
In Rust, F1 opens the console: type client.connect 139.99.142.169:23251. Launch Rust on this page does the same by opening the game through Steam and connecting.