RUST METRICSFlight deck · live data
Data live Servers11,881 Players89,789 Populated4,026 Fresh wipes 3 h157 Scan5 min
‹ All servers116.91.217.101:28125
Offline Full Queue Fresh wipe Wipe due No query

HomingValidation

Offline 116.91.217.101:28125 checked 14d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,405top 71%
Last wipe14d 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 71% 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

What wipe timing does HomingValidation follow?

The rhythm of HomingValidation's wipes cannot be told yet: too few 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. 14 days 14 hours ago the current world was made.

Tag meanings

How should you read the tags on HomingValidation?

These are the tags HomingValidation publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Build 167231; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does HomingValidation appear in Rust Metrics lists and filters?

Rust Metrics lists featuring HomingValidation: 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.

Player count

Where does HomingValidation sit in the rankings?

Player hours over seven days put HomingValidation at #15,405, in the top 71% of all ranked servers.

What player count does HomingValidation carry?

Reading for HomingValidation: offline at this moment; last seen 14 days 14 hours ago.

Operator and location

Which location does HomingValidation run from?

No region comes from HomingValidation. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 116.91.217.101:28125.

What Rust version is HomingValidation on?

Rust network protocol 2634 and build 167231 on Windows is the build HomingValidation runs. Matching protocol is required to join. Let Steam update your game.

How reliable is HomingValidation, and is it online now?

Check: connection. HomingValidation is offline at this moment. Last contact was 14 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 October 2026.

Rules and settings

How is HomingValidation configured, and what rules are in force?

Check: gather rate. The name HomingValidation does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is HomingValidation on?

Procedural map on HomingValidation, made by the game's generator.

Join

How can you get onto HomingValidation?

Check: join. Open Rust, press F1, then enter client.connect 116.91.217.101:28125. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Build 167231.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.