RUST METRICSFlight deck · live data
Data live Servers11,614 Players33,332 Populated2,810 Fresh wipes 3 h68 Scan5 min
‹ All servers57.128.229.173:25570
Offline Full Queue Fresh wipe Wipe due No query

A Rust Server

Offline 57.128.229.173:25570 checked 1d ago

moddedcarbon
COM 1 · connect

Server instruments

last reading Tue 15:00 UTC
0 10 20 30 40 PAX 2 /40

Players now

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

Server fps

48 h low 224 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 197,793 ×1000

Entities

48 h range 197,793–197,793 · memory 3,223 MB
1239 ET SINCE RESTART 00:50

Uptime

0 h 50 min since its last restart, at the last reading
7-day average2peak 5
Rank#4,728top 21%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Memory3,223MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5213:0014:0015:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040013:0014:0015: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 26 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
15k10k15k20k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 21% 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 gap2.4 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 26 OctFri 23 OctSat 17 Oct
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 06:01 UTC2d ago – – running 1
Mon 26 Oct, 09:55 UTC2d ago 5 – 0.8 days 1
Fri 23 Oct, 16:12 UTC5d ago 1 – 2.7 days 0
Sat 17 Oct, 14:01 UTC11d ago 1 halved by day 1 6.1 days 1
Wed 14 Oct, 13:54 UTC14d ago 1 – 3 days 0
Mon 12 Oct, 11:48 UTC16d ago 1 halved by day 1 2.1 days 0
Sat 3 Oct, 15:41 UTC25d ago 6 halved by day 1 8.8 days 1
Sat 3 Oct, 08:00 UTC25d ago 6 – 0.3 days 0
Fri 2 Oct, 19:38 UTC26d ago 6 – 0.5 days 0
Thu 1 Oct, 19:44 UTC FW27d ago 6 – 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 happens on A Rust Server when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. 5 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 1 when it didn't.

How often does A Rust Server wipe, and when?

There is no next wipe to predict: A Rust Server wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 2 days 20 hours ago the current world was made.

Tags

How should you read the tags on A Rust Server?

These are the tags A Rust Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. 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 A Rust Server?

On Rust Metrics, A Rust Server sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Occupancy

What position does A Rust Server hold among Rust servers?

Player hours over seven days put A Rust Server at #4,728, in the top 21% of all ranked servers.

How full does A Rust Server get?

Status for A Rust Server: offline. Last seen 39 hours ago. Seven-day check: 2 players on average. Peak reading: 5. The last 48 hours peaked at 13:00 UTC, averaging 2 players at that hour.

Server details

Where does A Rust Server sit?

No region tag on A Rust Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 57.128.229.173:25570.

What Rust version is A Rust Server on?

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

How does A Rust Server perform?

Check: fps. Average 224 server fps over the last 48 hours, low of 224. Within range. Peak entity count: 197,793. Buildings, deployables and all else included. Reading: 3,223 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is A Rust Server, and is it online now?

A Rust Server reports offline. The last reading came 39 hours ago. Reading: uptime. About 50 minutes ago it restarted, on its own count. Uptime for the last 7 full days: 25 of 168 hours, or 15%. The first sighting on Rust Metrics was 26 September 2026.

Rules and settings

What rules does A Rust Server enforce, and what are its settings?

No gather rate appears in the name: A Rust Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on A Rust Server?

From seed 1, the game generates the procedural map on A Rust Server. Its size is 6,000. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join A Rust Server?

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

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players 40 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.