RUST METRICSFlight deck · live data
Data live Servers11,709 Players55,398 Populated3,239 Fresh wipes 3 h162 Scan5 min
‹ All servers5.215.61.217:28015
Offline Full Queue Fresh wipe Wipe due No query

hoagaming-test

Offline 5.215.61.217:28015 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% 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#15,955top 72%
Last wipe23d agono schedule published
Next wipe–no wipe 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
15k10k15k20k6 Oct8 Oct9 Oct11 Oct12 Oct14 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

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 timing

When does hoagaming-test wipe?

To tell the rhythm of hoagaming-test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 1 hours ago.

Tag meanings

How should you read the tags on hoagaming-test?

These are the tags hoagaming-test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does hoagaming-test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry hoagaming-test: 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.

Population

Where does hoagaming-test sit in the rankings?

Ranking for hoagaming-test: #15,955 on seven-day player hours, top 72% of all ranked servers.

How full does hoagaming-test get?

Status for hoagaming-test: offline. Last seen 21 days 21 hours ago.

Operator and location

Which location does hoagaming-test run from?

No region tag on hoagaming-test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 5.215.61.217:28015.

What Rust version is hoagaming-test on?

Rust network protocol 2634 and build 166652 on Windows is the build hoagaming-test runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on hoagaming-test, and is it online?

hoagaming-test reports offline. The last reading came 21 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 6 October 2026.

Rules and settings

What rules does hoagaming-test enforce, and what are its settings?

Check: gather rate. The name hoagaming-test does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on hoagaming-test?

The game generates a procedural map for hoagaming-test.

Join

How can you get onto hoagaming-test?

Press F1 in Rust and enter client.connect 5.215.61.217:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.