RUST METRICSFlight deck · live data
Data live Servers11,800 Players69,961 Populated3,675 Fresh wipes 3 h123 Scan5 min
‹ All servers88.200.215.219:28125
Offline Full Queue Fresh wipe Wipe due No query

DATA5.2_Disposable

Offline 88.200.215.219:28125 checked 16d 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,549top 71%
Last wipe16d 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 12:18 UTC16d ago 0 – 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

Wipe schedule

What should you expect from wipe day on DATA5.2_Disposable?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does DATA5.2_Disposable follow?

Its rhythm cannot be told from the wipes of DATA5.2_Disposable on record: there are too few. 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 16 days 9 hours ago.

Tag meanings

How should you read the tags on DATA5.2_Disposable?

These are the tags DATA5.2_Disposable 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): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does DATA5.2_Disposable appear in Rust Metrics lists and filters?

On Rust Metrics, DATA5.2_Disposable sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does DATA5.2_Disposable sit in the rankings?

Player hours over seven days put DATA5.2_Disposable at #15,549, in the top 71% of all ranked servers.

How full does DATA5.2_Disposable get?

Reading for DATA5.2_Disposable: offline at this moment; last seen 16 days 9 hours ago.

Server details

Which location does DATA5.2_Disposable run from?

No region tag on DATA5.2_Disposable. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 88.200.215.219:28125.

What Rust version is DATA5.2_Disposable on?

Reading: DATA5.2_Disposable, Rust network protocol 2634 and build 167398, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is DATA5.2_Disposable up, and how often does it stay up?

Reading: offline. DATA5.2_Disposable last answered 16 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 12 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on DATA5.2_Disposable?

Check: gather rate. The name DATA5.2_Disposable does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on DATA5.2_Disposable?

Check: map. Procedural, generated by the game, on DATA5.2_Disposable.

Connection

What do you do to join DATA5.2_Disposable?

Press F1 in Rust and enter client.connect 88.200.215.219:28125. 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 mp1,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.