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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Force wipe
Thursday 1 October 2026, 18:06 UTC FW
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 average peak across its recent wipes is 0 players. Peak population on the latest wipe came 0 hours after it.
Once a month is all Rust solo PVE wipes, together with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. This world dates from 27 days 2 hours.
The Rust Live Stats lists that include Rust solo PVE are Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
gmvanilla (Game mode): Survival in the vanilla style; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded: that is the tag list Rust solo PVE publishes for the game's server browser. 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.
0 of Rust solo PVE's 50 slots are filled right now. Averaged over seven days: 0 players.
Player hours over seven days put Rust solo PVE at #15,348, in the top 69% of all ranked servers.
No gather rate appears in the name Rust solo PVE. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser files it under Modded: plugins or settings alter the game. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
A procedural map of 3,500 with seed 6738, generated by the game, runs on Rust solo PVE. Same size, same seed, same map: RustMaps has it, reachable from this page.
Nothing on Rust solo PVE states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 85.190.149.48:10900.
Server fps averaged 12 over the last 48 hours, with a low of 10. Buildings, deployables and everything else in the world added up to a maximum of 66,636 entities. The highest memory usage was 2,012 MB. A climbing entity count and low fps are felt as lag by players.
The setup on Rust solo PVE is Rust network protocol 2635 and build 168909 with Windows. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, Rust solo PVE is live. About 12 hours ago is when it last restarted, according to its uptime. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. On 13 September 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 85.190.149.48:10900.
