Rust Server TrendsSeismic network · station log
Recording Stations11,844 Players90,018 Active3,736 Wipes · 3 h420 48 h

Station AU-15090 · no signal

Rust Debug Compatibility Test

Offline 42.117.242.54:28025 checked 13d ago

Connect
Players now
0/ 5
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,090
top 70%
Last wipe
13d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station AU-15090 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 5 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 506 on average
215/ 275
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
286/ 350
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 282 on average
766/ 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 277 on average
46/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
873/ 950
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 242 on average
704/ 800
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Rust Debug Compatibility Test?

A procedural map runs on Rust Debug Compatibility Test, generated by the game.

Which settings and rules apply on Rust Debug Compatibility Test?

You will find no gather rate in the name of Rust Debug Compatibility Test. The group limit is not published. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on Rust Debug Compatibility Test?

Rust Debug Compatibility Test is not responding at this moment and is offline, last seen 13 days 4 hours ago.

How does Rust Debug Compatibility Test rank against other Rust servers?

Over the last seven days, Rust Debug Compatibility Test recorded enough player hours to reach #15,090 worldwide, placing it in the top 70% of all ranked servers.

Server details

How reliably does Rust Debug Compatibility Test stay online?

No contact with Rust Debug Compatibility Test right now, and the last recorded contact was 13 days 4 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 16 October 2026 is when Rust Server Trends first recorded it.

Which region does Rust Debug Compatibility Test run from?

No region comes from Rust Debug Compatibility Test, though its region code is au1. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 42.117.242.54:28025.

Which Rust version is Rust Debug Compatibility Test running?

Rust Debug Compatibility Test is running Rust network protocol 2573 and build 110006 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

On what timetable does Rust Debug Compatibility Test run its wipes?

On record so far are too few of Rust Debug Compatibility Test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 13 days 4 hours is how long the current world has been running.

Tags

What do the server tags on Rust Debug Compatibility Test mean?

The game's server browser reads the tags Rust Debug Compatibility Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): Slots: 5; v2573 (Protocol): To connect, your game must be on the same protocol, 2573; cs110006 (Build): Game build: 110006; ptrak (Networking): Network layer: RakNet, the standard for Rust; $rau1 (Region code): Region code: au1. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Rust Debug Compatibility Test appear?

The Rust Server Trends lists that take in Rust Debug Compatibility Test are: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.

How to join

What steps get you onto Rust Debug Compatibility Test?

To join, enter client.connect 42.117.242.54:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp5
Max players Slots: 5.
v2573
Protocol To connect, your game must be on the same protocol, 2573.
cs110006
Build Game build: 110006.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$rau1
Region code Region code: 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.