Rust Server TrendsSeismic network · station log
Recording Stations11,650 Players32,278 Active2,796 Wipes · 3 h79 48 h

Station XX-16615 · no signal

Firedasherskull's Server [AU]

Offline 51.161.145.147:23853 checked 27d ago

moddedoxide
Connect
Players now
0/ 40
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,615
top 70%
Last wipe
38d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16615 · 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 40 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, measured since 17 Sep. 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
15k10k15k20k20 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

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

Expected events

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 peak
4players, 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 4, 2 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 20 Sep, 08:48 UTC38d ago M0.5rising 4 – running 1

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
vanilla + OC · groups of 16+ · monthly · 1 on average
0/ 75
Rustafied.com - AU Main OC · groups of 16+ · weekly · 147 on average
290/ 150
Rustafied.com - AU Monday OC · groups of 16+ · weekly · 120 on average
84/ 100
Rustopia.gg - AU Main OC · groups of 12+ · weekly · 60 on average
61/ 150
Rustafied.com - AU Long OC · groups of 16+ · monthly · 31 on average
21/ 100
Rustafied.com - AU Friday OC · groups of 16+ · weekly · 29 on average
4/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Firedasherskull's Server [AU]?

Generated by the game, the map on Firedasherskull's Server [AU] is procedural, size 4,500 with seed 50000. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Firedasherskull's Server [AU]?

You will find no gather rate in the name of Firedasherskull's Server [AU]. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on Firedasherskull's Server [AU] right now?

Firedasherskull's Server [AU] is not responding at this moment and is offline, last seen 27 days 21 hours ago.

How does Firedasherskull's Server [AU] rank against other Rust servers?

Over the last seven days, Firedasherskull's Server [AU] recorded enough player hours to reach #16,615 worldwide, placing it in the top 70% of all ranked servers.

Operator and location

How reliably does Firedasherskull's Server [AU] stay online?

No contact with Firedasherskull's Server [AU] right now, and the last recorded contact was 27 days 21 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Firedasherskull's Server [AU] run from?

No region tag comes from Firedasherskull's Server [AU], though the name points to Oceania. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 51.161.145.147:23853.

What build of Rust does Firedasherskull's Server [AU] use?

On Linux, Firedasherskull's Server [AU] runs Rust network protocol 2633 and build 165217. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Firedasherskull's Server [AU]?

4 players, on average, was the busiest crowd at its recent wipes. 2 hours after the latest wipe, the crowd peaked.

How often does Firedasherskull's Server [AU] wipe, and on which days?

Too few wipes of Firedasherskull's Server [AU] are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 38 days 19 hours.

Server tags

What do the server tags on Firedasherskull's Server [AU] mean?

Tags published by Firedasherskull's Server [AU] and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 Firedasherskull's Server [AU] appear?

You will find Firedasherskull's Server [AU] on the following Rust Server Trends lists: Oceania Rust servers, live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Oceania; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Firedasherskull's Server [AU]?

To join, enter client.connect 51.161.145.147:23853 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 mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp40
Max players 40 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build The game build is 165217.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.