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 6d 23h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 1, 35 hours in.
Force wipe
Thursday 1 October 2026, 18:35 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.
At their busiest, its recent wipes averaged 1 players. 35 hours after the latest wipe, the crowd reached its peak.
Once a month is all breaking rustories 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. The world you are playing on was built 28 days 1 hours.
On Rust Live Stats, breaking rustories is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.
The server browser reads gmvanilla (Game mode): Survival in the vanilla style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): The server runs protocol 2634, so match that version to join; cs166494 (Build): Build: 166494; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game changes here through plugins or settings, so it is Modded, which breaking rustories publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
breaking rustories is carrying 0 players at the moment, with 50 slots in total. Averaged over seven days: 0 players.
Ranked by seven-day player hours, breaking rustories is #15,289, placing it in the top 69% of ranked servers.
Nothing in the name of breaking rustories states a gather rate. The default applies: 8 players to a group. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser files it under Modded: plugins or settings alter the game. The plugin load is Oxide. VAC is enabled: Valve's anti-cheat.
breaking rustories runs a game-generated procedural map: size 4,500, seed 5369. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on breaking rustories states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 15.204.174.114:28015 is its address.
It never went below 3 server fps in the last 48 hours, averaging 29. It supported up to 137,862 entities, covering buildings, deployables and all other objects. Up to 8,224 MB of memory was used. Players experience lag when fps is low and the entity count climbs.
The setup on breaking rustories is Rust network protocol 2634 and build 166494 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, breaking rustories is live. The uptime it reports puts the last restart at about 6 days 11 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 15.204.174.114:28015.