RUST METRICSFlight deck · live data
Data live Servers11,716 Players55,754 Populated3,252 Fresh wipes 3 h168 Scan5 min
‹ All servers160.251.201.172:28015
Online Full Queue Fresh wipe Wipe due No query

RustServer_5962

Online 160.251.201.172:28015 checked 6m ago

COM 1 · connect

Server instruments

last reading Thu 09:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 51 SERVER FPS

Server fps

48 h low 28 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 120,540 ×1000

Entities

48 h range 118,413–120,835 · memory 4,032 MB
1239 ET SINCE RESTART 6D 11H

Uptime

6 days 11 hours since its last restart, at the last reading
7-day average0peak 2
Rank#8,503top 38%
Last wipe8d agono schedule published
Next wipe–too few wipes seen yet
Memory4,032MBat the last reading
REC 1

Players

AveragePeak
0123411:0020:0005:0014:0000:0009:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608011:0020:0005:0014:0000:0009:00

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 38% 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 peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 18:36 UTC8d ago 2 – 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 happens on RustServer_5962 when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. 41 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does RustServer_5962 follow?

Its rhythm cannot be told from the wipes of RustServer_5962 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. 8 days 15 hours ago the current world was made.

Tag meanings

Which tags does RustServer_5962 carry, and what do they mean?

Tags published by RustServer_5962, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_5962 appear in Rust Metrics lists and filters?

On Rust Metrics, RustServer_5962 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; Last wipe: In the last 2 weeks.

Occupancy

Where does RustServer_5962 sit in the rankings?

Ranking for RustServer_5962: #8,503 on seven-day player hours, top 38% of all ranked servers.

What player count does RustServer_5962 carry?

0 of 10 slots are filled on RustServer_5962 right now. Seven-day check: 0 players on average. Peak reading: 2.

Operator and location

What location is RustServer_5962 hosted in?

No region comes from RustServer_5962. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 160.251.201.172:28015.

What Rust version is RustServer_5962 on?

Reading: RustServer_5962, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does RustServer_5962 perform?

Reading: 40 server fps on average across the last 48 hours. It never dropped below 28. Peak entity count: 120,835. Buildings, deployables and all else included. Reading: 4,893 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

Is RustServer_5962 up, and how often does it stay up?

Check: connection. RustServer_5962 is online at this moment. Reading: uptime. About 6 days 11 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What rules does RustServer_5962 enforce, and what are its settings?

No gather rate appears in the name: RustServer_5962. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. 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.

Which map is live on RustServer_5962?

Size 4,500 and seed 28423: the game generates the procedural map on RustServer_5962 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto RustServer_5962?

Press F1 in Rust and enter client.connect 160.251.201.172: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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.