RUST METRICSFlight deck · live data
Data live Servers11,633 Players48,252 Populated3,188 Fresh wipes 3 h102 Scan5 min
‹ All servers81.167.91.188:28000
Online Full Queue Fresh wipe Wipe due No query

4250_53158091

Online 81.167.91.188:28000 checked 11m ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,396top 69%
Last wipe22d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123410:0019:0004:0013:0022:0007:00

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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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.

usual gap19.1 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 5 OctWed 16 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 09:26 UTC22d ago 0 – running 0
Wed 16 Sep, 05:59 UTC42d ago 0 – 19.1 days 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 timing

What should you expect from wipe day on 4250_53158091?

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

How often does 4250_53158091 wipe, and when?

The rhythm of 4250_53158091'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. 22 days 23 hours ago the current world was made.

Tags

How should you read the tags on 4250_53158091?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from 4250_53158091. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does 4250_53158091 appear in Rust Metrics lists and filters?

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

Occupancy

Where does 4250_53158091 sit in the rankings?

Player hours over seven days put 4250_53158091 at #15,396, in the top 69% of all ranked servers.

What is the population on 4250_53158091?

0 of 10 slots are filled on 4250_53158091 right now. Seven-day reading: 0 players on average.

Server

What location is 4250_53158091 hosted in?

No region comes from 4250_53158091. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 81.167.91.188:28000.

What Rust version is 4250_53158091 on?

Reading: 4250_53158091, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is 4250_53158091 up, and how often does it stay up?

Reading: online. 4250_53158091 answers right now. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What settings and rules apply on 4250_53158091?

Reading the name gives no gather rate for 4250_53158091. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is 4250_53158091 on?

Procedural map on 4250_53158091, made by the game's generator.

Connection

How do you connect to 4250_53158091?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.