WARRIOR-RO | EU/RO | Vanilla+ | Biweekly
Online 51.89.8.206:28015 checked 8m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 21% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 07:06 UTC3d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
At their busiest, its recent wipes averaged 6 players. 5 hours after the latest wipe, the crowd peaked.
What is the wipe schedule on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Its rhythm cannot yet be told: too few of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly's wipes are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 3 days 15 hours ago the server made the world it is on now.
Population
How busy is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Of 125 slots on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, 0 are in use right now. The average across the last seven days is 0 players; the peak reached 6. Look at 19:00 UTC for the last 48 hours: that hour averaged 2 players.
How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly rank against other Rust servers?
Ranked #4,620 on seven-day player hours, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is in the top 21% of all ranked servers.
Rules and settings
Which map does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run?
The game generates the procedural map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which has size 4,000.
What are the rules and settings on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
No gather rate appears in the name WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. The group limit is 8 players, which is the game's default. The server runs survival, gather, build and raid in the standard game. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run?
Rust network protocol 2635 and build 168909 is the build WARRIOR-RO | EU/RO | Vanilla+ | Biweekly runs, on Linux. Steam updates your game for you, and the protocol has to match for you to join.
Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly online, and how reliable is it?
The server is up at the moment: WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is online. The uptime it reports puts the last restart at about 3 days 13 hours ago. It was up 143 of 144 hours across the last 6 full days, or 99% of the time. It first appears in Rust Heatmap records on 22 October 2026.
Where is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly located?
By its name, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly points to Europe, and it publishes no region tag. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 51.89.8.206:28015.
Does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run smoothly?
It averaged 230 server fps over the last 48 hours, with a low of 218. The world held as many as 94,864 entities, buildings and deployables included. Memory use reached 3,686 MB at most. Players feel lag when fps falls and the entity count climbs.
Tags
Which Rust Heatmap lists and filters include WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The Rust Heatmap lists that WARRIOR-RO | EU/RO | Vanilla+ | Biweekly fits are: EU Rust servers, busiest first and Modded Rust servers, by live population. These are the filters that return it on the list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
What do the server tags on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly mean?
The game's server browser reads the tags WARRIOR-RO | EU/RO | Vanilla+ | Biweekly publishes: gmrust (Game mode): Rust survival, standard rules; mp125 (Max players): Slot count: 125; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): This build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Press F1 in Rust to open the console, then enter client.connect 51.89.8.206:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.