WARRIOR-RO | EU/RO | Vanilla+ | Biweekly
Online 51.89.8.206:28015 checked 10m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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
Players each hour, from the hour of the wipe. The latest peaked at 6, 5 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
25 OCT 2026Sun 25 Oct, 07:06 UTC2d 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Settings and map
On WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which rules and settings apply?
No gather rate appears in the name WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. The default group limit of 8 players applies. The server runs survival, gather, build and raid: the standard game. Combat and raiding between players are possible. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in use on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
WARRIOR-RO | EU/RO | Vanilla+ | Biweekly runs on a procedural map. The game generates it, and its size is 4,000.
Tags
On Rust Server Index, which lists and filters carry WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
These lists on Rust Server Index take WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: Rust servers filed under Europe and Modded Rust servers, filed by play style. It appears under the following 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 3 days.
Which tags are attached to WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, and what do they stand for?
Filed under these tags, as published by WARRIOR-RO | EU/RO | Vanilla+ | Biweekly and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp125 (Max players): The queue ceiling sits at 125; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipes and resets
What should you expect on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly when wipe day comes?
At their busiest, its recent wipes drew 6 players on average. 5 hours into the latest wipe, the crowd reached its peak.
Which wipe timetable does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly follow?
WARRIOR-RO | EU/RO | Vanilla+ | Biweekly's rhythm cannot be told yet: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 2 days 11 hours.
Population
What position does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly hold among Rust servers?
The seven-day player-hours ranking places WARRIOR-RO | EU/RO | Vanilla+ | Biweekly at #4,711, among the top 21% of ranked servers.
What does the player count on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly look like?
The live count for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly stands at 0 players, out of 125 slots. Filed under seven-day figures: an average of 0 players and a peak of 6. Filed under busiest hour: 20:00 UTC in the last 48 hours, averaging 4 players.
Server details
Which Rust build is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly running?
Rust network protocol 2635 and build 168909 on Linux is what you will find on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
You will find WARRIOR-RO | EU/RO | Vanilla+ | Biweekly online as of now. About 2 days 9 hours ago, by its own uptime figure, is when it last restarted. It was up 96 of 96 hours across the last 4 full days, or 100% of the time. It was first recorded by Rust Server Index on 22 October 2026.
What is performance like on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The last 48 hours give an average of 231 server fps and a floor of 218. The entity count reached 94,874, covering buildings, deployables and all else in the world. Up to 3,335 MB of memory was in use. What players feel as lag is low fps together with a rising entity count.
What is the location of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
No region tag is published by WARRIOR-RO | EU/RO | Vanilla+ | Biweekly; the name it carries points to Europe. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 51.89.8.206:28015.
Connecting
What steps lead onto WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Enter client.connect 51.89.8.206:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp125,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp125
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.
