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
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 0, 0 hours in.
Force wipe
Thursday 1 October 2026, 18:12 UTC FW
Wipe
Wednesday 16 September 2026, 11:05 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 average peak across its recent wipes is 0 players. The crowd on the latest wipe peaked 0 hours in.
Heliloot's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 27 days 16 hours have passed since this world was generated.
These are the Rust Live Stats lists Heliloot fits: 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 gmrust (Game mode): Survival here follows standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): The server runs protocol 2634, so match that version to join; cs167584 (Build): Build: 167584; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded: plugins or changed settings alter the game, which Heliloot 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.
Heliloot is carrying 0 players at the moment, with 100 slots in total. Across the past week the average was 0 players.
Player hours over seven days put Heliloot at #15,338, in the top 69% of all ranked servers.
Nothing in the name of Heliloot states a gather rate. The default applies: 8 players to a group. It runs survival, 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.
Size 4,500, seed 1337: that is the procedural map the game generates for Heliloot. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on Heliloot states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 153.92.1.32:28015.
It never went below 23 server fps in the last 48 hours, averaging 46. Entity count reached 120,711: buildings, deployables and the rest of the world. Memory use peaked at 4,338 MB. A climbing entity count and low fps are felt as lag by players.
The setup on Heliloot is Rust network protocol 2634 and build 167584 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Right now Heliloot is online. The uptime it reports puts the last restart at about 6 days 2 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. On 13 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 153.92.1.32: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.