RUST METRICSFlight deck · live data
Data live Servers11,658 Players32,604 Populated2,794 Fresh wipes 3 h75 Scan5 min
‹ All servers133.88.123.166:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_8392

Offline 133.88.123.166:28015 checked 1d ago

COM 1 · connect

Server instruments

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

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 200 SERVER FPS

Server fps

48 h low 182 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 41,476 ×1000

Entities

48 h range 41,476–43,489 · memory 1,821 MB
1239 ET SINCE RESTART 3D 14H

Uptime

3 days 14 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,349top 69%
Last wipe8d agono schedule published
Next wipe–too few wipes seen yet
Memory1,821MBat the last reading
REC 1

Players

AveragePeak
0123405:0006:0008:0009:0011:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040005:0006:0008:0009:0011:0012: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 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

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
Tue 20 Oct, 07:11 UTC8d ago 0 – 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 timing

What happens on RustServer_8392 when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

When does RustServer_8392 wipe?

The rhythm of RustServer_8392's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 8 days 21 hours ago.

Tags

How should you read the tags on RustServer_8392?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; 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): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from RustServer_8392. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_8392 appear in Rust Metrics lists and filters?

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

Player count

Where does RustServer_8392 sit in the rankings?

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

What player count does RustServer_8392 carry?

RustServer_8392 is not responding; status offline, last seen 39 hours ago. Seven-day reading: 0 players on average.

Server details

Which location does RustServer_8392 run from?

No region comes from RustServer_8392. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 133.88.123.166:28015.

What Rust version is RustServer_8392 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by RustServer_8392. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for RustServer_8392?

Over the last 48 hours the average was 201 server fps; the floor was 182. Check: entities. The peak was 43,489, counting buildings, deployables and the rest of the world. Reading: 2,197 MB of memory at the highest. Expect lag when fps falls and entities climb.

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

Check: connection. RustServer_8392 is offline at this moment. Last contact was 39 hours ago. Reading: uptime. About 3 days 14 hours ago it restarted, on its own count. Reading: 79% uptime over the last 7 full days. It was up 133 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is RustServer_8392 configured, and what rules are in force?

Check: gather rate. The name RustServer_8392 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is RustServer_8392 on?

Check: map. Procedural, size 3,000, seed 22225, generated by the game on RustServer_8392. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join RustServer_8392?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
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 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.