RUST METRICSFlight deck · live data
Data live Servers11,716 Players60,383 Populated3,374 Fresh wipes 3 h178 Scan5 min
‹ All servers124.133.254.222:28015
Offline Full Queue Fresh wipe Wipe due No query

RustPersionalServise_

Offline 124.133.254.222:28015 checked 19d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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

REC 3

Rank

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

When does RustPersionalServise_ wipe?

Its rhythm cannot be told from the wipes of RustPersionalServise_ 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 20 days 1 hours ago.

Tag meanings

How should you read the tags on RustPersionalServise_?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from RustPersionalServise_. 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 RustPersionalServise_?

These Rust Metrics lists carry RustPersionalServise_: 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 RustPersionalServise_ sit in the rankings?

Player hours over seven days put RustPersionalServise_ at #15,817, in the top 72% of all ranked servers.

How full does RustPersionalServise_ get?

Reading for RustPersionalServise_: offline at this moment; last seen 19 days 2 hours ago.

Operator and location

Where does RustPersionalServise_ sit?

Reading: location. RustPersionalServise_ gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 124.133.254.222:28015.

What Rust version is RustPersionalServise_ on?

Reading: RustPersionalServise_, Rust network protocol 2634 and build 167398, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RustPersionalServise_, and is it online now?

RustPersionalServise_ reports offline. The last reading came 19 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on RustPersionalServise_?

Reading the name gives no gather rate for RustPersionalServise_. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RustPersionalServise_?

Check: map. Procedural, generated by the game, on RustPersionalServise_.

Connection

What do you do to join RustPersionalServise_?

To join: start Rust, press F1 and type client.connect 124.133.254.222:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.