RUST METRICSFlight deck · live data
Data live Servers11,626 Players40,809 Populated2,991 Fresh wipes 3 h88 Scan5 min
‹ All servers160.251.210.74:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_5208

Offline 160.251.210.74:28015 checked 20d 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,842top 72%
Last wipe20d 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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 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

Reset cycle

What wipe timing does RustServer_5208 follow?

The rhythm of RustServer_5208's wipes cannot be told yet: too few are on record. 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 20 days 8 hours ago.

Tag meanings

How should you read the tags on RustServer_5208?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2597 (Protocol): Protocol 2597: join only on the same game version; cs130842 (Build): The server runs game build 130842; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from RustServer_5208. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RustServer_5208?

These Rust Metrics lists carry RustServer_5208: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does RustServer_5208 hold among Rust servers?

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

What is the population on RustServer_5208?

Reading for RustServer_5208: offline at this moment; last seen 20 days 8 hours ago.

Server details

Where does RustServer_5208 sit?

No region comes from RustServer_5208. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 160.251.210.74:28015.

What Rust version is RustServer_5208 on?

Rust network protocol 2597 and build 130842 on Linux is the build RustServer_5208 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RustServer_5208, and is it online now?

Reading: offline. RustServer_5208 last answered 20 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for RustServer_5208. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is RustServer_5208 on?

Check: map. Procedural, size 3,000, seed 18229, generated by the game on RustServer_5208. View it on RustMaps from this page: matching size and seed give an identical map.

Join

What do you do to join RustServer_5208?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2597,gmrust,cs130842,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2597
Protocol Protocol 2597: join only on the same game version.
cs130842
Build The server runs game build 130842.
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.