Online 157.85.91.42:28015 checked 8m ago
Long Hours
Connect
srv = rust.server("157.85.91.42:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 57% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 08:20 UTC6d ago | 1 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())Map
6000 · seed 0- map
- Procedural Map
- size
- 6000
- seed
- –
Server
srv.info()- address
- 157.85.91.42:28015
- region
- –
- max players
- 50
- group limit
- teams off
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 08:50 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | TheLastOfRust Hardcore PvE Zombie Survival | no group limit · 8 on average | 1/100 |
| 1 | Nikki & Yuni Hardcore Solo/Duo | Wiped 10/15 | No Tech Tree | R | NA · no group limit · biweekly · 3 on average | 4/50 |
| 2 | Alone & Afraid | OC · no group limit · biweekly · 2 on average | 0/50 |
| 3 | [BR/LATAM] Evolution PVE | Hardcore Zombie Survival | SA · groups of 15+ · biweekly · 2 on average | 3/50 |
| 4 | TheLastOfRust Premium Hardcore PvE Zombie Survival | no group limit · 2 on average | 2/100 |
| 5 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 62/500 |
Quick answers
From the figures on this page.
Population data
What position does Long Hours take in the server rankings?
Over the last seven days Long Hours sits at #12,589 on player hours, in the top 57% of ranked servers.
How full does Long Hours run?
The sample now reads 0 players for Long Hours, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1.
About the server
What does performance look like on Long Hours?
Averaged over 48 hours: 74 server fps, never under 61. Buildings, deployables and all else in the world took the count as high as 200,317 entities. Memory peaked at 9,472 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does Long Hours run?
Version Rust network protocol 2634 and build 167781 on Linux is reported by Long Hours. Steam updates your game for you, but the protocol must match to join.
Is Long Hours up, and what does its uptime show?
Online is the state at the latest refresh for Long Hours. The uptime it reports puts the last restart about 6 days 11 hours ago. Uptime of 81% across the last 7 full days: 136 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Long Hours run from?
There is no region published for Long Hours. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.91.42:28015 is its address.
Settings and map
What rules and settings are recorded for Long Hours?
The name Long Hours carries no gather rate. No group limit is published. hardcore is the game mode here, and Facepunch's most punishing mode. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Long Hours?
A procedural map of size 6,000 runs on Long Hours, generated by the game.
Wipe data
On what schedule does Long Hours wipe?
The record for Long Hours holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 6 days 14 hours ago, and that is the one in play.
What is wipe day on Long Hours like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Tags, lists
Which Rust Data filters and lists contain Long Hours?
On Rust Data, Long Hours appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last week.
Which meanings do the tags on Long Hours hold?
These tags are published by Long Hours and read by the game's server browser: gmhardcore (Game mode): A harsher ruleset: hardcore; mp50 (Max players): The server lists 50 slots; ts0 (Group limit): Teams are disabled; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Long Hours?
The manual route: launch Rust, F1, then client.connect 157.85.91.42:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.