RUST METRICSFlight deck · live data
Data live Servers11,765 Players63,710 Populated3,546 Fresh wipes 3 h131 Scan5 min
‹ All servers175.197.111.242:28015
Offline Full Queue Fresh wipe Wipe due No query

HORIHEE RUNTIME LAB

Offline 175.197.111.242:28015 checked 27d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 1 /4

Players now

25% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,441top 60%
Last wipe33d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Sep27 Sep29 Sep2 Oct4 Oct7 Oct

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

PLAN

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.

usual gap0.6 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 25 SepThu 24 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 01:31 UTC32d ago 1 – running 1
Thu 24 Sep, 10:39 UTC33d ago 1 – 0.6 days 1

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on HORIHEE RUNTIME LAB?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does HORIHEE RUNTIME LAB follow?

To tell the rhythm of HORIHEE RUNTIME LAB, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 33 days 16 hours ago.

Tags

How should you read the tags on HORIHEE RUNTIME LAB?

Tags published by HORIHEE RUNTIME LAB, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show HORIHEE RUNTIME LAB?

These Rust Metrics lists carry HORIHEE RUNTIME LAB: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does HORIHEE RUNTIME LAB hold among Rust servers?

Ranking for HORIHEE RUNTIME LAB: #14,441 on seven-day player hours, top 60% of all ranked servers.

How full does HORIHEE RUNTIME LAB get?

Reading for HORIHEE RUNTIME LAB: offline at this moment; last seen 27 days 5 hours ago.

Operator and location

Which location does HORIHEE RUNTIME LAB run from?

No region comes from HORIHEE RUNTIME LAB. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 175.197.111.242:28015.

What Rust version is HORIHEE RUNTIME LAB on?

Rust network protocol 2633 and build 165217 on Windows is the build HORIHEE RUNTIME LAB runs. Matching protocol is required to join. Let Steam update your game.

Is HORIHEE RUNTIME LAB up, and how often does it stay up?

Check: connection. HORIHEE RUNTIME LAB is offline at this moment. Last contact was 27 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Settings and map

What rules does HORIHEE RUNTIME LAB enforce, and what are its settings?

Reading the name gives no gather rate for HORIHEE RUNTIME LAB. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is HORIHEE RUNTIME LAB on?

Check: map. Procedural, generated by the game, on HORIHEE RUNTIME LAB.

How to join

How do you connect to HORIHEE RUNTIME LAB?

To join: start Rust, press F1 and type client.connect 175.197.111.242:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players 4 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.