RUST METRICSFlight deck · live data
Data live Servers11,721 Players61,329 Populated3,285 Fresh wipes 3 h177 Scan5 min
‹ All servers24.42.149.142:28015
Online Full Queue Fresh wipe Wipe due No query

WHYPrintRust

Online 24.42.149.142:28015 checked 14m ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

Players now

0% full 7-day avg7-day peak
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 2
Rank#11,154top 50%
Last wipe28d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

AveragePeak
0123401:0010:0020:0005:0014:0023: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 Sep6 Oct13 Oct21 Oct29 Oct

Top 50% 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 gap13.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctWed 30 SepFri 4 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 23:15 UTC FW28d ago 2 – running 0
Wed 30 Sep, 23:26 UTC29d ago 2 – 1 days 0
Fri 4 Sep, 23:28 UTC55d ago – – 26 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 WHYPrintRust when wipe day comes?

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

How often does WHYPrintRust wipe, and when?

There is no next wipe to predict: WHYPrintRust 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. 28 days 1 hours ago the current world was made.

Lists and filters

How should you read the tags on WHYPrintRust?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; 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 from WHYPrintRust. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does WHYPrintRust appear in Rust Metrics lists and filters?

Rust Metrics lists featuring WHYPrintRust: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does WHYPrintRust sit in the rankings?

Player hours over seven days put WHYPrintRust at #11,154, in the top 50% of all ranked servers.

What player count does WHYPrintRust carry?

0 of 20 slots are filled on WHYPrintRust right now. Check: players over seven days. Average 0, peak 2.

Server

What location is WHYPrintRust hosted in?

No region tag on WHYPrintRust. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 24.42.149.142:28015.

What Rust version is WHYPrintRust on?

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

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

Check: connection. WHYPrintRust is online at this moment. Reading: 85% uptime over the last 7 full days. It was up 143 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: WHYPrintRust. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is off. That is Valve's anti-cheat.

What map is WHYPrintRust on?

Check: map. Procedural, generated by the game, on WHYPrintRust.

Connection

How do you connect to WHYPrintRust?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players The server holds 20 slots.
ts8
Group limit Default limit in force: 8 per team.
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.

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.