RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers185.83.154.140:28025
Online Full Queue Fresh wipe Wipe due No query

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

Online EU 185.83.154.140:28025 checked 12m ago

3x quad biweekly wipes vanillamoddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

last reading Wed 20:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

0% 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 80,276 ×1000

Entities

48 h range 75,730–82,205 · memory 3,672 MB
1239 ET SINCE RESTART 3D 05H

Uptime

3 days 5 hours since its last restart, at the last reading
7-day average0peak 4
Rank#4,765top 21% · #1651 in EU
Last wipe3d agobiweekly schedule
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Memory3,672MB48 h peak 4 players
REC 1

Players
AveragePeak
0123423:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

REC 2

Server performance
01020304023:0008:0017:0001:0010: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 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
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 21% of all ranked servers, top 56% in EU, and #304 of the quad servers (top 37%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

usual gap7 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak2players, last three wipes
crowd held60%else halves by day 1.5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 20hFW
  2. WPT 2Tue 10 Nov, 14:57 UTC12d 16h
  3. WPT 3Sat 14 Nov, 14:57 UTC16d 16h
  4. WPT 4Wed 18 Nov, 14:57 UTC20d 16h
  5. WPT 5Sun 22 Nov, 14:57 UTC24d 16h
  6. WPT 6Thu 3 Dec, 19:00 UTC35d 20hFW
  7. WPT 7Tue 8 Dec, 14:57 UTC40d 16h
  8. WPT 8Sat 12 Dec, 14:57 UTC44d 16h

The first 48 hours of its last wipes

Sun 25 OctWed 21 OctSat 17 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 14:57 UTC3d ago 2 – running 0
Wed 21 Oct, 14:57 UTC7d ago 2 held half 4 days 0
Sat 17 Oct, 14:57 UTC11d ago 3 halved by day 2 4 days 0
Tue 13 Oct, 14:57 UTC15d ago 3 held half 4 days 0
Fri 9 Oct, 14:57 UTC19d ago 3 halved by day 1 4 days 0
Mon 5 Oct, 14:57 UTC23d ago 3 held half 4 days 0
Thu 1 Oct, 19:25 UTC FW27d ago 5 held half 3.8 days 1
Sun 27 Sep, 14:57 UTC31d ago 3 held half 4.2 days 0
Wed 23 Sep, 14:57 UTC35d ago 1 halved by day 3 4 days 0
Sat 19 Sep, 14:57 UTC39d ago 2 held half 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 happens on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 2 hours. Until the next wipe, the crowd stayed above half that peak in 60% of its recent wipes. By day 1.5 it fell below half when it didn't.

When does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J wipe?

every 4 weeks on Tuesday, Wednesday, Saturday and Sunday at 14:57 UTC is how GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 3 days 7 hours ago. The tags carry an every-two-weeks wipe schedule.

Tags

Which tags does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J carry, and what do they mean?

These are the tags GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp200 (Max players): Slots: 200; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $rDE (Region code): Region code reading: DE; ^b (Biweekly): Two-week wipe schedule; ^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): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which operator is behind GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

The grub.army hostname on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J also appears on 3 other servers we track, which points to one operator.

Where does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J appear in Rust Metrics lists and filters?

On Rust Metrics, GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sits in these lists: 3x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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 week; Gather rate: 3x.

Population

What position does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hold among Rust servers?

Top 21% of all ranked servers: GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J takes #4,765 on seven-day player hours and #1,651 in Europe. Check: group rank. #304 among quad servers.

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

0 of 200 slots are filled on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J right now. Check: players over seven days. Average 0, peak 4. The last 48 hours peaked at 19:00 UTC, averaging 3 players at that hour.

Server

What location is GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hosted in?

Reading: location. The EU tag puts GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 185.83.154.140:28025.

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

Rust network protocol 2635 and build 168909 on Linux is the build GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Reading: 30 server fps on average across the last 48 hours. It never dropped below 30. Check: entities. The peak was 82,205, counting buildings, deployables and the rest of the world. Reading: 4,238 MB of memory at the highest. Expect lag when fps falls and entities climb.

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

Check: connection. GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is online at this moment. Check: restart. The uptime it reports puts the last restart about 3 days 5 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Gather rate check: 3x. That comes from the name GRUB.ARMY EU 3X 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. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

What map is GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J on?

Check: map. Procedural, size 3,500, seed 1337, generated by the game on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Connection

What do you do to join GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

Check: join. Open Rust, press F1, then enter client.connect 185.83.154.140:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

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 Survival on vanilla settings.
mp200
Max players Slots: 200.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$rDE
Region code Region code reading: DE.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

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 The server browser files it under Europe.

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.