At press time 11,830 servers89,192 players415 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 4,623

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly

Online 51.89.8.206:28015 checked 13m ago

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is a Rust server. At the last count it had 0 players of a possible 125; over the past week it averaged 0, with a peak of 6. It stands at No. 4,623 of the ranked servers, the top 21%. It last wiped 4d ago. Its own tags class it as modded, oxide.

§ 1Attendance

AveragePeak
00.250.50.75122:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

§ 2Performance

010020030040022:0007:0016:0002:0011:0020:00

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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 21% of all ranked servers. Ranked on player hours over the last seven days.

§ 4The wipe scheduletoo few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

The rhythm
Wipe-day peak6

players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 5 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers 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.

§ 6In its own wordsas the server describes itself

;WARRIOR-RO EU/RO Vanilla+ Biweekly 🇷🇴 RO: Rust Vanilla+ Wipe la 2 săptămâni Upkeep 75% PvP & Raids 🇬🇧 EN: Rust Vanilla+ Wipe every 2 weeks 75% Upkeep PvP & Raids

§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 МИНИ-КАРТА 2Х | STORM | FPS+ 28.10129/100 EU · groups of 8+ · weekly · 128 on average
  2. 2 RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10109/225 EU · groups of 16+ · weekly · 119 on average
  3. 3 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.1034/700 EU · groups of 16+ · monthly · 96 on average
  4. 4 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10110/700 EU · groups of 16+ · monthly · 92 on average
  5. 5 RustSpain.com | EU Main346/350 EU · groups of 12+ · weekly · 85 on average
  6. 6 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.1013/1000 EU · groups of 16+ · monthly · 84 on average

§ 8Questions answeredfrom the figures in this entry

Server details

What Rust version is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on?

The server WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must be on the same protocol; Steam handles the update.

How reliable is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly, and is it online now?

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly currently answers as online. A restart came about 4 days 9 hours ago, by the server's own uptime figure. The records show 99% uptime over the last 6 full days: 143 of 144 hours up. Its earliest entry at Rust Server Stats is dated 22 October 2026.

How does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly perform?

Server fps averaged 228 over the last 48 hours; the low was 213. Of note: 94,826 entities at the peak, counting buildings, deployables and the rest. Up to 3,786 MB of memory was used. What players feel as lag: fps running low and entities climbing.

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. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. At 51.89.8.206:28015 stands the address.

Rules, settings, map

The map for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: which one is it?

WARRIOR-RO | EU/RO | Vanilla+ | Biweekly runs a procedural map, generated by the game, of size 4,000.

What settings and rules does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run?

Nothing in the name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly gives a gather rate. The group limit is 8 players, the game's default. Play is survival, gather, build and raid: the standard game. Raiding and fighting other players are allowed. It sits in the Modded section, with plugins or settings that change play. The plugin set is Oxide. VAC, Valve's anti-cheat, is enabled.

The players

How full does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly get?

The record for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly shows 0 players, against a capacity of 125. Over seven days the mean is 0 players, with a peak of 6. At 19:00 UTC, over the last 48 hours, the mean was 1 players, the highest of any hour.

Where does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly sit in the rankings?

On player hours over seven days WARRIOR-RO | EU/RO | Vanilla+ | Biweekly ranks #4,623, inside the top 21% of all ranked servers.

The tags and lists

Where does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly appear among the Rust Server Stats lists and filters?

The Rust Server Stats lists WARRIOR-RO | EU/RO | Vanilla+ | Biweekly fits: EU Rust servers: the records and Modded Rust servers. On the server list it comes up under these filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

How should the tags on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly be read?

The game's server browser reads the tags WARRIOR-RO | EU/RO | Vanilla+ | Biweekly publishes: gmrust (Game mode): The standard survival game; mp125 (Max players): The server holds 125 slots; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a framework for plugins, runs here; ^z (Modded): Under Modded, because settings or plugins alter the game. At the top of this page are its current players, queue and world creation time, all taken from the tags.

The wipes

What is the shape of wipe day on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Averaged over recent wipes, the crowd reached 6 at its busiest. 5 hours after the latest wipe, the crowd peaked.

On what schedule does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly wipe?

Too few wipes of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly are on record to establish its rhythm. The monthly force wipe falls on every Rust server alike, and Thursday 5 November at 19:00 UTC is the next one. The present world dates from 4 days 10 hours.

Connection

Which steps join WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

To connect, open the console with F1 in Rust and enter client.connect 51.89.8.206:28015. The Launch Rust and join button on this page does the same through Steam.

§ 9Key to the tagswhat each one means

Published as mp125,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The standard survival game.
mp125
Max players The server holds 125 slots.
ts8
Group limit Set at the game default of 8 per team.
v2635
Protocol Join only on protocol 2635; other versions cannot connect.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Oxide (uMod), a framework for plugins, runs here.
^z
Modded Under Modded, because settings or plugins alter the game.

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.