WARRIOR-RO | EU/RO | Vanilla+ | Biweekly
Online 51.89.8.206:28015 checked 11m ago
Server instruments
last reading Thu 08:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 213 · below 20 is lag, below 10 is badEntities
48 h range 92,376–94,864 · memory 3,201 MBUptime
3 days 21 hours since its last restart, at the last readingPlayers
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 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 127/100
- 187/225
- 75/700
- 9/200
- 18/1000
- 216/700
Quick answers
from the figures on this pageReset cycle
What happens on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly when wipe day comes?
At their busiest, its recent wipes drew 6 players on average. Peak crowd on the latest wipe: 5 hours in.
What wipe timing does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly follow?
To tell the rhythm of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 3 days 23 hours ago.
Lists and filters
Which tags does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly carry, and what do they mean?
Tags published by WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp125 (Max players): Slots: 125; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
On Rust Metrics, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. These filters bring it up 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.
Occupancy
Where does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly sit in the rankings?
Player hours over seven days put WARRIOR-RO | EU/RO | Vanilla+ | Biweekly at #4,594, in the top 21% of all ranked servers.
How full does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly get?
Current headcount on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: 0 players, 125 slots available. Seven-day check: 0 players on average. Peak reading: 6. The last 48 hours peaked at 19:00 UTC, averaging 2 players at that hour.
Server details
What location is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly hosted in?
Check: location. No region tag comes from WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, but the name points to Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 51.89.8.206:28015.
What Rust version is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on?
Reading: WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly perform?
Reading: 229 server fps on average across the last 48 hours. It never dropped below 213. Check: entities. The peak was 94,864, counting buildings, deployables and the rest of the world. Memory peak: 3,686 MB. What players call lag comes from low fps and an entity count on the rise.
Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly up, and how often does it stay up?
Check: connection. WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is online at this moment. Reading: uptime. About 3 days 21 hours ago it restarted, on its own count. Reading: 99% uptime over the last 6 full days. It was up 143 of 144 hours. Reading: first seen 22 October 2026, recorded by Rust Metrics.
Settings and map
How is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly configured, and what rules are in force?
Check: gather rate. The name WARRIOR-RO | EU/RO | Vanilla+ | Biweekly does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
What map is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on?
Size 4,000: a procedural map on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, made by the game.
Connection
How can you get onto WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?
To join: start Rust, press F1 and type client.connect 51.89.8.206:28015. Or press Launch Rust here and Steam opens the game and connects you.