Rust Server TrendsSeismic network · station log
Recording Stations11,621 Players40,134 Active2,833 Wipes · 3 h132 48 h

Station XX-3644 · recording

RustServer_25919

Online 160.251.169.111:28015 checked 9m ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 4
Rank
#3,644
top 16%
Last wipe
10d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-3644 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−2into Thu 15:00 UTC
Peak · 48 h
3most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123405:0014:0000:0009:0018:0003:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020005:0014:0000:0009:0018:0003: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 19 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 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Expected events

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 gap
11.7 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
50%else halves by day 1

The first 48 hours of its last wipes

Mon 19 OctThu 8 OctSat 26 Sep
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 19 Oct, 14:18 UTC10d ago M0.0rising 3 – running 2
Thu 8 Oct, 14:50 UTC21d ago M0.5rising 3 held half 11 days 0
Sat 26 Sep, 03:42 UTC34d ago M0.0rising 2 halved by day 1 12.5 days 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
ShockRust | Blue | NoLimit no group limit · 151 on average
29/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average
55/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
10/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
29/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
53/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RustServer_25919?

RustServer_25919 runs a procedural map of size 3,000 with seed 15754, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on RustServer_25919?

The name of RustServer_25919 gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on RustServer_25919 right now?

A reading taken now shows 0 players on RustServer_25919, which has 50 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 4. Averaged over the last 48 hours, the busiest hour was 14:00 UTC at 2 players.

How does RustServer_25919 rank against other Rust servers?

On player hours for the past week, RustServer_25919 sits at #3,644, which puts it inside the top 16% of every ranked server.

Server facts

How reliably does RustServer_25919 stay online?

Right now, you can reach RustServer_25919. Going by the uptime figure it reports, it restarted about 5 days 4 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. 19 September 2026 is when Rust Server Trends first recorded it.

Does RustServer_25919 hold a steady tick rate?

The 48-hour average is 167 server fps; 129 is the lowest observed. The world held up to 47,353 entities at its peak, buildings and deployables included. Memory use peaked at 3,492 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does RustServer_25919 run from?

A region is not published by RustServer_25919. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 160.251.169.111:28015.

Which Rust version is RustServer_25919 running?

Rust network protocol 2635 and build 168909 on Linux is what RustServer_25919 runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on RustServer_25919?

3 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 1 hours after the wipe. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.

On what timetable does RustServer_25919 run its wipes?

There is no next wipe to predict at RustServer_25919, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 10 days 14 hours.

Tags

What do the server tags on RustServer_25919 mean?

These are the tags RustServer_25919 publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does RustServer_25919 appear?

These Rust Server Trends lists include RustServer_25919: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Join the server

How do you connect to RustServer_25919?

Enter client.connect 160.251.169.111:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.