LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 23% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The current map
Wednesday 28 October 2026, 06:49 UTC
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.
The record holds too few of Solo War's wipes to reveal its rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 34 hours have passed since this world was generated.
These are the Rust Live Stats lists Solo War fits: Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days it appears on the server list.
These are the tags Solo War makes public: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Plugins or settings changes put this under Modded. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
Solo War is carrying 0 players at the moment, with 10 slots in total. Peak over the past week: 3. Average: 1 players. Peak hour over 48 hours: 08:00 UTC, at 3 players on average.
Ranked by seven-day player hours, Solo War is #5,152, placing it in the top 23% of ranked servers.
The name Solo War carries no gather rate. The default applies: 8 players to a group. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
Solo War runs a game-generated procedural map: size 4,000, seed 1410201025. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on Solo War states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 139.99.142.169:23251.
It never went below 115 server fps in the last 48 hours, averaging 176. It supported up to 93,932 entities, covering buildings, deployables and all other objects. Memory use peaked at 3,941 MB. Players experience lag when fps is low and the entity count climbs.
Solo War operates on Linux with Rust network protocol 2635 and build 168909. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, Solo War is live. Based on the uptime it reports, the last restart was about 12 hours ago. It was online for 15 of 24 hours in the last 1 full day, or 62% of the time. The first sighting by Rust Live Stats was on 27 October 2026.
Enter client.connect 139.99.142.169:23251 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.