RUST METRICSFlight deck · live data
Data live Servers11,722 Players62,389 Populated3,280 Fresh wipes 3 h180 Scan5 min
‹ All servers42.117.242.54:28025
Offline Full Queue Fresh wipe Wipe due No query

Rust Debug Compatibility Test

Offline 42.117.242.54:28025 checked 13d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

Players now

0% full 7-day avg
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 –
Rank#15,090top 70%
Last wipe13d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 schedule

How often does Rust Debug Compatibility Test wipe, and when?

Its rhythm cannot be told from the wipes of Rust Debug Compatibility Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 13 days 7 hours ago.

Tag meanings

How should you read the tags on Rust Debug Compatibility Test?

These are the tags Rust Debug Compatibility Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; v2573 (Protocol): Match the game version: protocol 2573 is required; cs110006 (Build): Build 110006; ptrak (Networking): This is RakNet, Rust's usual network layer; $rau1 (Region code): Region code reading: au1. 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 Rust Debug Compatibility Test?

Rust Metrics lists featuring Rust Debug Compatibility Test: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.

Occupancy

Where does Rust Debug Compatibility Test sit in the rankings?

Player hours over seven days put Rust Debug Compatibility Test at #15,090, in the top 70% of all ranked servers.

What player count does Rust Debug Compatibility Test carry?

Reading for Rust Debug Compatibility Test: offline at this moment; last seen 13 days 7 hours ago.

Server details

Which location does Rust Debug Compatibility Test run from?

No region tag on Rust Debug Compatibility Test, whose region code is au1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 42.117.242.54:28025.

What Rust version is Rust Debug Compatibility Test on?

Version check: Rust network protocol 2573 and build 110006 on Windows, run by Rust Debug Compatibility Test. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Rust Debug Compatibility Test, and is it online now?

Check: connection. Rust Debug Compatibility Test is offline at this moment. Last contact was 13 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 October 2026.

Map and rules

How is Rust Debug Compatibility Test configured, and what rules are in force?

No gather rate appears in the name: Rust Debug Compatibility Test. No group limit is published. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is Rust Debug Compatibility Test on?

Check: map. Procedural, generated by the game, on Rust Debug Compatibility Test.

Connection

How do you connect to Rust Debug Compatibility Test?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$rau1,v2573,gmrust,cs110006

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players Slots: 5.
v2573
Protocol Match the game version: protocol 2573 is required.
cs110006
Build Build 110006.
ptrak
Networking This is RakNet, Rust's usual network layer.
$rau1
Region code Region code reading: au1.

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.