Players now
Live- Full
- 0%
- In queue
- 0
- Peak, 48 hours
- 2
- Peak, 7 days
- 6
0% full
Rank
top 21%
7-day average
peak 6
Last wipe
no schedule published
Next wipe
too few wipes seen yet
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
daily · 1 is bestTop 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
Wipes
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 1 134/ 100
- 2 82/ 225
- 3 25/ 700
- 4 3/ 200
- 5 5/ 1000
- 6 94/ 700
Quick answers
from the figures on this pageServer details
Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly online, and how reliable is it?
WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is up and taking players now. The uptime it reports puts its last restart about 3 days 18 hours ago. Over the last 6 full days, 143 of 144 hours were online: 99%. The first time Rust Dashboard recorded it was 22 October 2026.
Which version of Rust does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run?
Rust network protocol 2635 and build 168909 is running on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which sits on Linux. Joining needs the same protocol on your side, and Steam handles that update.
Where is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly located?
No region tag comes from WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, though the name points to Europe. Rust Dashboard takes the location a server gives; the machine's real position is not checked. You'll connect at 51.89.8.206:28015.
Does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run smoothly?
Across the last 48 hours the average was 229 fps, with a floor of 218. At its highest the count reached 94,864 entities: buildings, deployables and the rest. It drew as much as 3,686 MB of memory at peak. Players feel lag when fps drops and the entity count climbs.
Lists
Which Rust Dashboard lists and filters include WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
You'll find WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on these themed lists at Rust Dashboard: Europe's Rust servers, live and Modded Rust servers, live now. It appears under these filters when you browse 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.
What do the server tags on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly mean?
The game's server browser reads these tags from WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: gmrust (Game mode): Standard Rust survival is the game mode; mp125 (Max players): 125 is the slot count; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Your game needs to be on the same version, protocol 2635, to get in; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): RakNet is the standard network layer for the game, and it is what runs here; $r? (Region code): No region code is set; ^o (Oxide): This server runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it appears under Modded. At the top of this page you'll find the current players, the queue and the world's creation time, which the tags carry too.
Player counts
How busy is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
As things stand, 0 players are on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which holds 125 slots. Averaged across the last seven days: 0 players, peaking at 6. The busiest point in the last 48 hours was 19:00 UTC, averaging 2 players.
How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly rank against other Rust servers?
Player hours over seven days put WARRIOR-RO | EU/RO | Vanilla+ | Biweekly at #4,621, in the top 21% of all ranked servers.
Reset times
What does wipe day look like on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The average busiest point of its recent wipes was 6 players. Peak crowd on the latest wipe came 5 hours after it began.
What is the wipe schedule on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
WARRIOR-RO | EU/RO | Vanilla+ | Biweekly has too few wipes on record yet for its rhythm to be seen. The monthly force wipe applies to every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was generated 3 days 19 hours ago.
Map and rules
What are the rules and settings on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
No gather rate appears in the name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly. 8 players per group is the game's default, and that is the cap here. It runs survival, gather, build and raid: the standard game. Raids and player fights are part of the game here. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. The anti-cheat from Valve, VAC, is active.
Which map does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run?
The game generates the procedural map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, size 4,000.
Join
How do I join WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The console in Rust opens with F1, and client.connect 51.89.8.206:28015 goes in there. Launch Rust on this page is the other route, opening Rust through Steam to connect you.
