RUST METRICSFlight deck · live data
Data live Servers11,694 Players52,148 Populated3,104 Fresh wipes 3 h109 Scan5 min
‹ All servers133.88.99.247:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_4201

Offline 133.88.99.247: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,869top 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 9 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 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_4201 follow?

The rhythm of RustServer_4201's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 20 days 22 hours ago.

Tags

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

These are the tags RustServer_4201 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): The server runs game build 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 RustServer_4201 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_4201: 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.

Population

What position does RustServer_4201 hold among Rust servers?

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

How full does RustServer_4201 get?

RustServer_4201 is not responding; status offline, last seen 20 days 9 hours ago.

Operator and location

Where does RustServer_4201 sit?

No region tag on RustServer_4201. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 133.88.99.247:28015.

What Rust version is RustServer_4201 on?

Version check: Rust network protocol 2634 and build 167398 on Linux, run by RustServer_4201. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on RustServer_4201, and is it online?

RustServer_4201 reports offline. The last reading came 20 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 9 October 2026.

Rules and settings

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

Reading the name gives no gather rate for RustServer_4201. 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. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_4201 on?

Size 3,000 and seed 25916: the game generates the procedural map on RustServer_4201 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join RustServer_4201?

Check: join. Open Rust, press F1, then enter client.connect 133.88.99.247: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?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build The server runs game build 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.