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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 19% 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.
Players each hour, from the hour of the wipe. The latest peaked at 4, 3 hours in.
The current map
Friday 23 October 2026, 14:16 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.
At their busiest, its recent wipes averaged 4 players. The crowd on the latest wipe peaked 3 hours in.
The record holds too few of Etho's Badlands's wipes to reveal its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 6 days 2 hours have passed since this world was generated.
The Rust Live Stats lists that include Etho's Badlands are 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 week it appears on the server list.
These are the tags Etho's Badlands makes public: gmrust (Game mode): Survival here follows standard Rust; mp40 (Max players): The slot count is 40; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.
Live now: 0 players on Etho's Badlands, out of 40 slots. The seven-day average is 1 players, with a peak of 4. Between now and 48 hours back, 17:00 UTC drew the most players, 3 on average.
On player hours for the past seven days, Etho's Badlands sits at #4,163, inside the top 19% of ranked servers.
No gather rate appears in the name Etho's Badlands. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, and the browser lists it as Modded. The plugin load is Oxide. VAC is enabled: Valve's anti-cheat.
Size 3,000, seed 50000: that is the procedural map the game generates for Etho's Badlands. RustMaps shows it from this page, since equal size and seed give an equal map.
No region is published by Etho's Badlands. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 203.16.163.243:24072 is its address.
The average server fps was 192 over the last 48 hours; the lowest was 117. Buildings, deployables and everything else in the world added up to a maximum of 49,979 entities. The highest memory usage was 3,760 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 168909 on Linux is what Etho's Badlands runs. Steam updates it for you, but your game needs the same protocol to join.
Etho's Badlands is up and running at this moment. About 46 hours ago is when it last restarted, according to its uptime. 119 of 120 hours were online in the last 5 full days, giving 99% uptime. On 23 October 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 203.16.163.243:24072.