Rust Server TrendsSeismic network · station log
Recording Stations11,766 Players65,323 Active3,462 Wipes · 3 h190 48 h

Station XX-15318 · recording

Long Hours

Online 157.85.91.42:28015 checked 7m ago

teams off moddedoxidehardcore
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,318
top 69%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15318 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123413:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

025507510013:0022:0007:0015:0001:0010:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

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.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 22 Oct, 08:20 UTC7d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
TheLastOfRust Hardcore PvE Zombie Survival no group limit · 7 on average
2/ 100
Nikki & Yuni Hardcore Solo/Duo | Wiped 10/15 | No Tech Tree | R NA · no group limit · biweekly · 3 on average
2/ 50
Alone & Afraid OC · no group limit · biweekly · 2 on average
3/ 50
[BR/LATAM] Evolution PVE | Hardcore Zombie Survival SA · groups of 15+ · biweekly · 2 on average
0/ 50
2/ 100
ほしラス2 EA · no group limit · 1 on average
1/ 50
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Long Hours?

Long Hours runs a procedural map of size 6,000, produced by the game.

Which settings and rules apply on Long Hours?

You will find no gather rate in the name of Long Hours. The group limit is not published. In hardcore mode, Facepunch's most punishing mode. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on Long Hours?

A reading taken now shows 0 players on Long Hours, which has 50 slots. The population averaged 0 players over the past week.

How does Long Hours rank against other Rust servers?

On player hours for the past week, Long Hours sits at #15,318, which puts it inside the top 69% of every ranked server.

Server facts

How reliably does Long Hours stay online?

As recorded now, Long Hours is running. The uptime it reports puts its last restart about 7 days ago. It was up 95% of the time across the last 7 full days: 159 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Does Long Hours hold a steady tick rate?

Across the last 48 hours it averaged 74 server fps, with a floor of 61. The world held up to 200,455 entities at its peak, buildings and deployables included. Its highest memory use was 9,472 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is Long Hours hosted?

No region is published by Long Hours. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 157.85.91.42:28015.

What build of Rust does Long Hours use?

Long Hours is running Rust network protocol 2634 and build 167781 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Long Hours?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe.

On what timetable does Long Hours run its wipes?

The rhythm of Long Hours cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 7 days 3 hours is how long the current world has been running.

Server tags

What do the server tags on Long Hours mean?

Tags published by Long Hours and read by the game's server browser include gmhardcore (Game mode): The game mode is hardcore, a harsher ruleset; mp50 (Max players): 50 slots are available; ts0 (Group limit): Teams are disabled; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Long Hours appear?

The Rust Server Trends lists that take in Long Hours are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 2 weeks.

Connecting

How do you connect to Long Hours?

To join, enter client.connect 157.85.91.42:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmhardcore,cs167781,ts0,^o^z

Game

gmhardcore
Game mode The game mode is hardcore, a harsher ruleset.
mp50
Max players 50 slots are available.
ts0
Group limit Teams are disabled.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build The game build is 167781.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.