StatusLive Servers online11,624 Players41,406 Populated3,010 Wiped · 3 h84 Interval5 min Date29 OCT 2026

DWG RG-S4613Server sheetchecked 11m ago

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

Online 51.89.8.206:28015 checked 11m ago

moddedoxide
Connect
Players now 0/ 125 0% full
7-day average0peak 6
Rank#4,613top 21%
Last wipe3d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
00.511.5208:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Fig. 1Players on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly
Fig. 2

Server performance

010020030040008:0017:0002:0011:0021:0006: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.

Fig. 2FPS, entities and memory
Fig. 3

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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

too few wipes seen yet

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

wipe-day peak6players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
128 / 100
02
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
124 / 225
03
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
44 / 700
04
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
3 / 200
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
19 / 1000
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 79 on average
155 / 700
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly online, and what uptime has been recorded?

At this moment WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is online. About 3 days 19 hours ago is when it last restarted, measured from the uptime it reports. 143 of 144 hours up over the last 6 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 22 October 2026.

Is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly stable in the figures recorded?

The last 48 hours give an average of 229 server fps and a floor of 213. Counted at its highest: 94,864 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,686 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Europe is where the name of WARRIOR-RO | EU/RO | Vanilla+ | Biweekly points, with no region tag published. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 51.89.8.206:28015 is its address.

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

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

Counts

How many players are plotted on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Current player count on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: 0, of 125 slots. Averaged across seven days, the player count is 0, with a peak of 6. Over the last 48 hours the busiest hour was 19:00 UTC, at an average of 2 players.

What rank has been recorded for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Over the last seven days, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly records #4,613 for player hours: the top 21% of all ranked servers.

Wipe data

What is recorded on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly on wipe day?

The recent wipes averaged a busiest count of 6 players. 5 hours after the latest wipe, the crowd peaked.

Which times and days are wipes plotted at on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

Too few wipes are on record for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 3 days 21 hours ago.

Settings

Which settings does WARRIOR-RO | EU/RO | Vanilla+ | Biweekly run, and what rules?

Gather rate for WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly played?

Generated by the game and procedural, the map measures 4,000 on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly.

Lists and filters

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

On Rust Graphs, WARRIOR-RO | EU/RO | Vanilla+ | Biweekly is placed in these lists: Europe servers, plotted and Modded Rust servers. These filters on the server list return it: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meaning is attached to each tag on WARRIOR-RO | EU/RO | Vanilla+ | Biweekly?

The game's server browser reads these tags from WARRIOR-RO | EU/RO | Vanilla+ | Biweekly: gmrust (Game mode): Standard survival, as Rust plays; mp125 (Max players): 125 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

How to join

How is WARRIOR-RO | EU/RO | Vanilla+ | Biweekly joined?

Enter client.connect 51.89.8.206:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp125
Max players 125 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

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.

KeyTag string decoded