Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO Z SRV11,615online PAX38,895playing OCC2,943with players WIPED 3H85
MODModded traffic
Callsign

WRR4613=

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

Online 51.89.8.206:28015 checked 7m ago

moddedoxide
Clearance · join
Players now 0/ 125 0% full
7-day average0peak 6
Rank#4,613top 21%
Last wipe3d agono schedule published
Next wipe–too few wipes seen yet
Track history

Players

AveragePeak
00.511.5208:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Server performance

010020030040008:0017:0002:0011:0021:0006: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

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

Flight plan

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 peak6players, 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 07:06 UTC4d ago 6 – running 1

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 128/100
  2. 02MOD
    Callsign RTR811EU · groups of 16+ · weekly · 118 on average RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
    Players 112/225
  3. 03MOD
    Callsign RUS021EU · groups of 16+ · monthly · 93 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 40/700
  4. 04MOD
    Callsign RST016EU · groups of 12+ · weekly · 88 on average RustSpain.com | EU Main
    Players 4/200
  5. 05MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 12/1000
  6. 06MOD
    Callsign RUS029EU · groups of 16+ · monthly · 79 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
    Players 132/700
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

On Rust Tracker, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly sits in these lists: EU Rust servers, tracked live and Modded servers, tracked live. It comes up 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.

Which tags does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly carry, and what do they mean?

These tags are published by WARRIOR-RO | EU/RO | Vanilla+ | Biweekly for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp125 (Max players): Capacity: 125 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Times

What happens on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on wipe day?

Recent wipes averaged a peak of 6 players. 5 hours after the latest wipe, the crowd peaked.

Which wipe times are confirmed for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly's rhythm cannot be told yet: too few wipes on record. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 3 days 20 hours.

Location and Status

What is the uptime on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, and is it online?

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is up and online at this moment. The uptime it reports puts the last restart about 3 days 19 hours ago. 99% uptime over the last 6 full days, with 143 of 144 hours up. The first sighting by Rust Tracker was 22 October 2026.

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

Rust network protocol 2635 and build 168909 is the build on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly; the platform is Linux. Steam updates it for you; your game must share the protocol to join.

Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly holding performance?

Server fps held an average of 229 across the last 48 hours, never below 213. Peak entity count: 94,864, covering buildings, deployables and all else in the world. It drew as much as 3,686 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.

Where does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly sit?

The name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly points to Europe, though no region tag is published. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 51.89.8.206:28015.

Population

Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly busy?

Slots 125; players on board 0: that is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly now. Peak of 6 in the last seven days, average 0 players. Busiest window in 48 hours: 19:00 UTC, 2 players on average.

What rank does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly carry among Rust servers?

Seven-day player hours put WARRIOR-RO | EU/RO | Vanilla+ | Biweekly at #4,613, within the top 21% of all ranked servers.

Settings

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

No gather rate appears in WARRIOR-RO | EU/RO | Vanilla+ | Biweekly's name. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

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

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

Connect

What is the way to join WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Open the console in Rust with F1 after starting the game, then type client.connect 51.89.8.206:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp125
Max players Capacity: 125 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; 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.