RUST METRICSFlight deck · live data
Data live Servers11,726 Players49,195 Populated3,240 Fresh wipes 3 h114 Scan5 min
‹ All servers188.190.43.8:28025
Offline Full Queue Fresh wipe Wipe due No query

TRIAGED Staging Retest

Offline 188.190.43.8:28025 checked 7d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 1 /2

Players now

50% full 7-day avg7-day peak
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 average1peak 1
Rank#13,133top 59%
Last wipe34d 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 Sep30 Sep6 Oct16 Oct22 Oct28 Oct

Top 59% 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.

wipe-day peak1players, 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 24 Sep, 18:38 UTC34d ago 1 – running 0

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

Reset cycle

What happens on TRIAGED Staging Retest when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does TRIAGED Staging Retest follow?

Its rhythm cannot be told from the wipes of TRIAGED Staging Retest on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 34 days 5 hours ago.

Lists and filters

How should you read the tags on TRIAGED Staging Retest?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168700 (Build): Build 168700; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from TRIAGED Staging Retest. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TRIAGED Staging Retest appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TRIAGED Staging Retest: 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

What position does TRIAGED Staging Retest hold among Rust servers?

Player hours over seven days put TRIAGED Staging Retest at #13,133, in the top 59% of all ranked servers.

What is the population on TRIAGED Staging Retest?

TRIAGED Staging Retest is not responding; status offline, last seen 7 days 15 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

Where does TRIAGED Staging Retest sit?

No region comes from TRIAGED Staging Retest. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.190.43.8:28025.

What Rust version is TRIAGED Staging Retest on?

Reading: TRIAGED Staging Retest, Rust network protocol 2635 and build 168700, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TRIAGED Staging Retest, and is it online now?

TRIAGED Staging Retest reports offline. The last reading came 7 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 24 September 2026.

Settings and map

What rules does TRIAGED Staging Retest enforce, and what are its settings?

Check: gather rate. The name TRIAGED Staging Retest does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TRIAGED Staging Retest?

Procedural map on TRIAGED Staging Retest, made by the game's generator.

How to join

What do you do to join TRIAGED Staging Retest?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2635,gmrust,cs168700,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players 2 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168700
Build Build 168700.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.