WARRIOR-RO | EU/RO | Vanilla+ | Biweekly
Online 51.89.8.206:28015 checked 11m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
every wipe as a delivery, newest first-
Sun 25 Oct, 07:06 UTC 07:06 UK · 3d agoWipe delivered
- Peak
- 6
- Crowd
- –
- Lasted
- running
- Players before
- 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.
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 120 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 32 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 16 / 700
- RustSpain.com | EU Main 4 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 2 / 1000
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 57 / 700
Quick answers
From the figures on this page.
Player count
How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly compare with other Rust servers in the rankings?
In the top 21% of all ranked servers sits WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, at #4,620 on hours played over seven days.
What is the current population on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
At the moment 0 players are on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which has 125 slots. Averaged over the past week: 0 players, peaking at 6. The busiest hour over the last 48 hours was 19:00 UTC, averaging 2 players.
Server rules
What is the current map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Size 4,000 is the procedural map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, which the game generates.
Which settings and rules apply on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly gives no gather rate. The game's default applies: 8 players to a group at most. It runs survival, the usual game: build, gather, raid. Fighting and raiding between players is allowed. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Oxide. VAC, Valve's anti-cheat, is switched on.
Operator and location
What is the location of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
The name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly points to Europe, though no region tag is published. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. 51.89.8.206:28015 is its address.
Does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly perform well?
Server fps over the last 48 hours averaged 230; the lowest was 218. The world held as many as 94,864 entities: buildings, deployables and the rest. 3,686 MB of memory was its top figure. Lag, to players, means low fps alongside an entity count on the rise.
Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly up, and how good is its uptime?
Right now, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is online. The uptime it reports puts its last restart at about 3 days 13 hours ago. It was up 143 of 144 hours over the last 6 full days, 99% of the time. 22 October 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly using?
On Linux, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly runs Rust network protocol 2635 and build 168909. The same protocol is required to join, and Steam takes care of updating it.
Map resets
What happens on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly when wipe day arrives?
The average busiest point of its recent wipes was 6 players. On the latest wipe, 5 hours passed before the crowd peaked.
On what schedule does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly reset its map?
To tell its rhythm we would need more of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly's wipes on record; there are too few yet. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. 3 days 15 hours have passed since this world was made.
Tags and filters
On Rust Wipe Tracker, which lists and filters is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly part of?
These Rust Wipe Tracker lists take WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: Rust servers in Europe and Modded Rust servers. On the server list, apply Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week and it appears.
What is the meaning of the server tags on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
gmrust (Game mode): Standard Rust survival is the game mode here; mp125 (Max players): It holds 125 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): A region code isn't set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing are the tags WARRIOR-RO | EU/RO | Vanilla+ | Biweekly publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
Getting started
What is the process to join WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 51.89.8.206:28015.