Rust Server TrendsSeismic network · station log
Recording Stations11,735 Players53,199 Active3,345 Wipes · 3 h133 48 h

Station XX-4622 · recording

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly

Online 51.89.8.206:28015 checked 10m ago

moddedoxide
Connect
Players now
0/ 125
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 6
Rank
#4,622
top 21%
Last wipe
3d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-4622 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 125 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Tue 18:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5200:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040000:0009:0018:0003:0012:0022: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 22 Oct. 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
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 21% 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
6players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 5 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 25 Oct, 07:06 UTC3d ago M0.7rising 6 – 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
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
46/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average
54/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
7/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
8/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 77 on average
100/ 700
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

The procedural map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is size 4,000, generated by the game.

Which settings and rules apply on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

No gather rate appears in the name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

0 of the 125 slots on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly are filled right now. Averaged across the last seven days the population was 0 players, reaching a peak of 6. Averaged over the last 48 hours, the busiest hour was 19:00 UTC at 2 players.

How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly rank against other Rust servers?

The last seven days of player hours place WARRIOR-RO | EU/RO | Vanilla+ | Biweekly at #4,622, in the top 21% of all ranked servers.

Server facts

How reliably does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly stay online?

Right now, you can reach WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. Its reported uptime points to a restart about 3 days 11 hours ago. 120 of 120 hours in the last 5 full days were up time, 100% of the total. On 22 October 2026 it was recorded for the first time by Rust Server Trends.

Does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly hold a steady tick rate?

Across the last 48 hours it averaged 230 server fps, with a floor of 218. Buildings, deployables and all the rest of the world's entities brought it to a high of 94,864. It reached a ceiling of 3,686 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run from?

Its name points to Europe, but WARRIOR-RO | EU/RO | Vanilla+ | Biweekly publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 51.89.8.206:28015.

Which Rust version is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly running?

Rust network protocol 2635 and build 168909 on Linux is what WARRIOR-RO | EU/RO | Vanilla+ | Biweekly runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

6 players, on average, was the busiest crowd at its recent wipes. 5 hours into the latest wipe, the crowd reached its peak.

How often does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly wipe, and on which days?

On record so far are too few of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly'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. The present world dates from 3 days 12 hours.

Lists and tags

What do the server tags on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly mean?

These are the tags WARRIOR-RO | EU/RO | Vanilla+ | Biweekly publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp125 (Max players): Slots: 125; 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): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 WARRIOR-RO | EU/RO | Vanilla+ | Biweekly appear?

The Rust Server Trends lists that take in WARRIOR-RO | EU/RO | Vanilla+ | Biweekly are: EU Rust servers and Modded Rust servers, tracked live. You will find it under these filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Connecting

How do you connect to WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Enter client.connect 51.89.8.206: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 mp125,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp125
Max players Slots: 125.
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 The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.