RUST METRICSFlight deck · live data
Data live Servers11,620 Players32,059 Populated2,776 Fresh wipes 3 h73 Scan5 min
‹ All servers85.1.29.131:28015
Online Full Queue Fresh wipe Wipe due No query

REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

Online 85.1.29.131:28015 checked 14m ago

COM 1 · connect

Server instruments

last reading Thu 04:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

48 h low 133 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 48,772 ×1000

Entities

48 h range 46,652–49,367 · memory 1,836 MB
1239 ET SINCE RESTART 2D 21H

Uptime

2 days 21 hours since its last restart, at the last reading
7-day average0peak 1
Rank#12,825top 58%
Last wipe10d agono schedule published
Next wipe–no rhythm it keeps
Memory1,836MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75106:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020006:0015:0000:0009:0019:0004: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 Sep27 Sep4 Oct12 Oct22 Oct29 Oct

Top 58% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap8.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Sun 18 OctFri 2 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 18:12 UTC10d ago 0 – running 0
Fri 2 Oct, 06:48 UTC26d ago 1 halved by day 3 16.5 days 0
Thu 1 Oct, 03:04 UTC28d ago 0 – 1.2 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

Reset cycle

What should you expect from wipe day on REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 41 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 3 it fell below half.

What wipe timing does REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE follow?

There is no next wipe to predict: REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 10 days 11 hours ago the current world was made.

Lists and filters

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

Check: tags. The game's server browser reads 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; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE appear in Rust Metrics lists and filters?

Rust Metrics lists featuring REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE: 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.

Population

What position does REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE hold among Rust servers?

Player hours over seven days put REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE at #12,825, in the top 58% of all ranked servers.

What is the population on REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?

Current headcount on REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 17:00 UTC, averaging 1 players at that hour.

Server

Where does REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE sit?

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

What Rust version is REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE on?

Rust network protocol 2635 and build 168909 on Linux is the build REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?

Check: fps. Average 161 server fps over the last 48 hours, low of 133. Within range. Check: entities. The peak was 49,367, counting buildings, deployables and the rest of the world. Memory peak: 2,039 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Check: connection. REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE is online at this moment. Check: restart. The uptime it reports puts the last restart about 2 days 21 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?

Check: gather rate. The name REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE on?

From seed 190440001, the game generates the procedural map on REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE. Its size is 3,000. 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 REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,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.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.