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 57% 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 1, 1 hours in.
The current map
Thursday 22 October 2026, 08:20 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 1 players. The crowd on the latest wipe peaked 1 hours in.
Too few wipes are recorded for Long Hours to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. This world dates from 5 days 16 hours.
The Rust Live Stats lists that include Long Hours are Modded Rust servers live now. Under the filters Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last week it appears on the server list.
The server browser reads gmhardcore (Game mode): A harsher ruleset: hardcore; mp50 (Max players): Slots: 50; ts0 (Group limit): There are no teams here; v2634 (Protocol): The server runs protocol 2634, so match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer — the game's standard one; $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, which Long Hours 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.
0 of Long Hours's 50 slots are filled right now. The seven-day average is 0 players, with a peak of 1.
Ranked by seven-day player hours, Long Hours is #12,586, placing it in the top 57% of ranked servers.
Nothing in the name of Long Hours states a gather rate. Group limits are not published. hardcore applies here, Hardest of Facepunch's modes. Raiding and player combat are both permitted. The server browser files it under Modded: plugins or settings alter the game. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
Long Hours runs a game-generated procedural map of size 6,000.
Nothing on Long Hours states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 157.85.91.42:28015 is its address.
It never went below 61 server fps in the last 48 hours, averaging 74. It supported up to 200,254 entities, covering buildings, deployables and all other objects. The highest memory usage was 9,049 MB. Players experience lag when fps is low and the entity count climbs.
Rust network protocol 2634 and build 167781 on Linux is what Long Hours runs. To join, your game must use the same protocol; Steam handles the update for you.
Long Hours is up and running at this moment. Based on the uptime it reports, the last restart was about 5 days 14 hours ago. It was online for 136 of 168 hours in the last 7 full days, or 81% of the time. Rust Live Stats has tracked it since 13 September 2026.
Enter client.connect 157.85.91.42: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.