Working its way up from the back of the class: #12,863 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 1,480 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Horizon | Rust LAB. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 78.240.69.79:28015.
Is Horizon | Rust LAB up, and how steady is its uptime?
At this moment, Horizon | Rust LAB is offline; the last time it was seen was 12 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 15 October 2026.
What Rust version is Horizon | Rust LAB on?
You will find Horizon | Rust LAB on Rust network protocol 2634 and build 167781, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Horizon | Rust LAB reset?
The record holds too few of Horizon | Rust LAB's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 14 days 12 hours have passed since this world was made.
Player count
Where does Horizon | Rust LAB place in the wider field of Rust servers?
In the top 60% of all ranked servers, Horizon | Rust LAB sits at #12,863 for player hours over the last seven days.
How many players does Horizon | Rust LAB usually have?
Horizon | Rust LAB is offline at the moment; the last time it was seen was 12 days 17 hours ago.
Tags
What do Horizon | Rust LAB's tags stand for?
The game's browser takes its cue from the tags Horizon | Rust LAB has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): Its slot count is 2; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Horizon | Rust LAB?
Rust Server Score lists that include Horizon | Rust LAB: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Horizon | Rust LAB set up, and what rules does it keep?
You will find no gather rate in the name of Horizon | Rust LAB. The default of 8 players applies as the group cap. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on Horizon | Rust LAB?
The game generates a procedural map for Horizon | Rust LAB.
How to join
How should you connect to Horizon | Rust LAB?
To connect, start Rust, press F1, and type client.connect 78.240.69.79:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max playersIts slot count is 2.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Even marks across the subjects, from F to F.