RUST METRICSFlight deck · live data
Data live Servers11,744 Players55,501 Populated3,172 Fresh wipes 3 h123 Scan5 min
‹ All servers135.148.134.77:22904
Online Full Queue Fresh wipe Wipe due No query

1

Online 135.148.134.77:22904 checked 55m ago

COM 1 · connect

Server instruments

last reading Fri 00:00 UTC
0 31 62 94 125 PAX 0 /125

Players now

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

Server fps

48 h low 54 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 116,289 ×1000

Entities

48 h range 102,367–118,476 · memory 4,109 MB
1239 ET SINCE RESTART 11:00

Uptime

11 h 0 min since its last restart, at the last reading
7-day average0peak –
Rank#15,284top 69%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet
Memory4,109MBat the last reading
REC 1

Players

AveragePeak
0123402:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020002:0011:0021:0006:0015:0000: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 13 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
15k10k15k20k13 Oct16 Oct20 Oct23 Oct27 Oct30 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 13 Oct, 11:48 UTC16d 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

Reset cycle

What should you expect from wipe day on 1?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does 1 wipe, and when?

The rhythm of 1'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. 16 days 13 hours ago the current world was made.

Tags

How should you read the tags on 1?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp125 (Max players): Slots: 125; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from 1. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show 1?

On Rust Metrics, 1 sits in these lists: 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 1 hold among Rust servers?

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

What player count does 1 carry?

Current headcount on 1: 0 players, 125 slots available. Check: player average. 0 over the last seven days.

Operator and location

Where does 1 sit?

Reading: location. 1 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 135.148.134.77:22904.

What Rust version is 1 on?

Rust network protocol 2635 and build 168909 on Linux is the build 1 runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for 1?

Reading: 122 server fps on average across the last 48 hours. It never dropped below 54. Reading: 118,476 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,809 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is 1, and is it online now?

Reading: online. 1 answers right now. By its reported uptime, the last restart was roughly 11 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on 1?

Check: gather rate. The name 1 does not state one. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is 1 on?

Size 4,500 and seed 50000: the game generates the procedural map on 1 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto 1?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp125
Max players Slots: 125.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
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.