RUST METRICSFlight deck · live data
Data live Servers11,652 Players32,618 Populated2,799 Fresh wipes 3 h77 Scan5 min
‹ All servers185.83.154.139:28025
Online Full Queue Fresh wipe Wipe due No query

GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J

Online EU 185.83.154.139:28025 checked 14m ago

2x quad biweekly wipes vanillamoddedcarbon
COM 1 · connect

Server instruments

last reading Thu 03:00 UTC
0 50 100 150 200 PAX 2 /200

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 75,366 ×1000

Entities

48 h range 72,279–75,953 · memory 3,370 MB
1239 ET SINCE RESTART 1D 12H

Uptime

1 days 12 hours since its last restart, at the last reading
7-day average1peak 3
Rank#3,900top 18% · #1427 in EU
Last wipe1d agobiweekly schedule
Next wipe2d 10hSat 31 Oct, 14:57 UTC
Memory3,370MB48 h peak 3 players
REC 1

Players

AveragePeakWipe
0123405:0014:0023:0008:0017:0003:00Wiped Tue 27 Oct, 14:57 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
01020304005:0014:0023:0008:0017:0003:00Wiped Tue 27 Oct, 14:57 UTCWIPE

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 18% of all ranked servers, top 49% in EU, and #259 of the quad servers (top 31%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

a steady gap

Next wipe Saturday 31 October, 14:57 UTC, in 2d 10h. Every 4 days · medium confidence

usual gap4 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak3players, last three wipes
crowd held25%else halves by day 3

Coming wipes

  1. WPT 1Sat 31 Oct, 14:57 UTC2d 10h
  2. WPT 2Wed 4 Nov, 14:57 UTC6d 10h
  3. WPT 3Thu 5 Nov, 19:00 UTC7d 14hFW
  4. WPT 4Sun 8 Nov, 14:57 UTC10d 10h
  5. WPT 5Thu 12 Nov, 14:57 UTC14d 10h
  6. WPT 6Mon 16 Nov, 14:57 UTC18d 10h
  7. WPT 7Fri 20 Nov, 14:57 UTC22d 10h
  8. WPT 8Tue 24 Nov, 14:57 UTC26d 10h

The first 48 hours of its last wipes

Fri 23 OctMon 19 OctThu 15 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 14:57 UTC1d ago – – running 0
Fri 23 Oct, 14:58 UTC5d ago 3 halved by day 3 4 days 1
Mon 19 Oct, 14:57 UTC9d ago 4 held half 4 days 0
Thu 15 Oct, 14:57 UTC13d ago 1 halved by day 3 4 days 0
Sun 11 Oct, 14:57 UTC17d ago 0 – 4 days 0
Wed 7 Oct, 14:57 UTC21d ago 1 halved by day 1 4 days 0
Sat 3 Oct, 14:57 UTC25d ago 2 halved by day 1 4 days 0
Thu 1 Oct, 18:19 UTC FW27d ago 2 – 1.9 days 0
Tue 29 Sep, 14:57 UTC29d ago 3 held half 2.1 days 0
Fri 25 Sep, 14:57 UTC33d ago 5 halved by day 2 4 days 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

An average of 3 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 1 hours. Until the next wipe, the crowd stayed above half that peak in 25% of its recent wipes. When it didn't hold, by day 3 it fell below half.

What wipe timing does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J follow?

The recent wipe interval on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is about 4 days. Saturday 31 October at 14:57 UTC is when its next wipe is due. The world it runs now was made 37 hours ago. A wipe schedule of every two weeks is published in its tags.

Tag meanings

How should you read the tags on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

These are the tags GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): The server holds 200 slots; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $rDE (Region code): The code for this server's region is DE; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here; EU (Europe): Europe is the browser category it sits in. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Who is in charge of GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Most likely the same operator runs them: GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J publishes a grub.army hostname, and so do 3 other servers we track.

Which lists and filters on Rust Metrics show GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Rust Metrics lists featuring GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J: 2x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 3 days; Gather rate: 2x.

Population

Where does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sit in the rankings?

Ranked by seven-day player hours, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sits at #3,900 and #1,427 in Europe, inside the top 18%. The quad group places it at #259.

What player count does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J carry?

Current headcount on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J: 2 players, 200 slots available. Check: players over seven days. Average 1, peak 3. Average at the busiest hour was 2 players, at 20:00 UTC over the last 48 hours.

Server

Which location does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J run from?

GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J gives Europe as its location, with the EU tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.83.154.139:28025.

What Rust version is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J on?

Rust network protocol 2635 and build 168909 on Linux is the build GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs. Matching protocol is required to join. Let Steam update your game.

How does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J perform?

Over the last 48 hours the average was 30 server fps; the floor was 30. Check: entities. The peak was 75,953, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,853 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, and is it online now?

GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J reports online. Status: normal. Reading: uptime. About 36 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

How is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J configured, and what rules are in force?

Gather rate check: 2x. That comes from the name GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J. The group cap is 4 players, read as quad. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. It describes itself as vanilla. The meaning given: the stock game: Facepunch's rates, kits and rules, unchanged. VAC is on. That is Valve's anti-cheat.

Which map is live on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Size 3,500 and seed 1337: the game generates the procedural map on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J from them. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Custom Map.

Join

How do you connect to GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

To join: start Rust, press F1 and type client.connect 185.83.154.139:28025. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/grubarmy is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$rDE,v2635,^z,^y,^b,^v,EU,gmvanilla,cs168909,ts4

Game

gmvanilla
Game mode The mode is vanilla survival.
mp200
Max players The server holds 200 slots.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$rDE
Region code The code for this server's region is DE.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

Region

EU
Europe Europe is the browser category it sits in.

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.