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 37% 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 13h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 1, 29 hours in.
Force wipe
Thursday 1 October 2026, 21:14 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 1 players. 29 hours after the latest wipe, the crowd reached its peak.
Nothing wipes Zomsaba_RUST3 but the force wipe, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world dates from 27 days 8 hours.
On Rust Live Stats, Zomsaba_RUST3 is listed under 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.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The slot count is 20; 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): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded, which Zomsaba_RUST3 publishes. 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.
Live now: 0 players on Zomsaba_RUST3, out of 20 slots. Averaged across seven days, 0 players; the peak was 1. The busiest hour in the past 48 was 10:00 UTC, averaging 1 players.
Player hours over seven days put Zomsaba_RUST3 at #8,320, in the top 37% of all ranked servers.
Nothing in the name of Zomsaba_RUST3 states a gather rate. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. Modded is its browser category, where plugins or settings change the game. The plugin load is Oxide. VAC is enabled: Valve's anti-cheat.
Zomsaba_RUST3 runs a game-generated procedural map: size 4,000, seed 19686. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on Zomsaba_RUST3 states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 162.43.37.59:28015 is its address.
The average server fps was 105 over the last 48 hours; the lowest was 61. Entity count reached 94,179: buildings, deployables and the rest of the world. The highest memory usage was 2,747 MB. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on Zomsaba_RUST3 is Rust network protocol 2635 and build 168909 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
Right now Zomsaba_RUST3 is online. About 6 hours ago is when it last restarted, according to its uptime. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. Rust Live Stats has tracked it since 13 September 2026.
Enter client.connect 162.43.37.59:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.