Rust Server TrendsSeismic network · station log
Recording Stations11,739 Players51,557 Active3,316 Wipes · 3 h122 48 h

Station EU-3988 · recording

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
Connect
Players now
1/ 200
0% full
Motion · 24 h
M0.0rising
+1 players on the day
7-day average
1
peak 3
Rank
#3,988
top 18% · #1450 in EU
Last wipe
1d ago
biweekly schedule
Next wipe
2d 15h
Sat 31 Oct, 14:57 UTC
Seismic record · station EU-3988 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 200 slots
Motion · 24 h
M0.0rising+1 players
Sharpest hour
+1into Tue 20:00 UTC
Peak · 48 h
3most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
0123400:0009:0018:0003:0012:0022:00Wiped Tue 27 Oct, 14:57 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
01020304000:0009:0018:0003:0012:0022: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Expected events

Wipe schedule

a steady gap

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

usual gap
4 daysbetween real wipes
on rhythm
75%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
25%else halves by day 3

Coming wipes

  1. 2d 15hSat 31 Oct, 14:57 UTC
  2. 6d 15hWed 4 Nov, 14:57 UTC
  3. 7d 19hThu 5 Nov, 19:00 UTCFW
  4. 10d 15hSun 8 Nov, 14:57 UTC
  5. 14d 15hThu 12 Nov, 14:57 UTC
  6. 18d 15hMon 16 Nov, 14:57 UTC
  7. 22d 15hFri 20 Nov, 14:57 UTC
  8. 26d 15hTue 24 Nov, 14:57 UTC

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.

Event catalogue

Wipes

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

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[RU] MAALVI RUST | X2 EU · quad · 2x · biweekly · 1 on average
0/ 100
Free Fields 2x | Noob Friendly EU · quad · 2x · biweekly · 1 on average
0/ 100
Atlas - EU 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip EU · quad · 2x · monthly · 557 on average
408/ 550
WARBANDITS.GG EU 2X |Solo/Duo/Trio/Quad|X2 JUST WIPED EU · quad · 2x · weekly · 210 on average
138/ 200
EU RENEGADE 2x Monthly | Solo Duo Trio Quad | 50% Upkeep | No B EU · quad · 2x · monthly · 144 on average
81/ 150
EU Limitless 2x Monthly Duo/Trio/Quad|No BP Wipes|Noob Friendly EU · quad · 2x · monthly · 134 on average
93/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

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

GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs a procedural map of size 3,500 with seed 1337, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.

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

2x gather is what GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs, judging by its name. 4 players is the most a group can hold (quad). It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. By its own description it is vanilla: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J right now?

1 of the 200 slots on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J are filled right now. The seven-day average is 1 players, with a peak of 3. The busiest point in the last 48 hours came at 20:00 UTC, averaging 2 players.

How does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J rank against other Rust servers?

The last seven days of player hours place GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J at #3,988, in the top 18% of all ranked servers and #1,450 in Europe. It sits at #256 among quad servers.

Server details

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

As recorded now, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is running. The uptime it reports puts its last restart about 31 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

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

Across the last 48 hours it averaged 30 server fps, with a floor of 30. The world held up to 75,760 entities at its peak, buildings and deployables included. It reached a ceiling of 3,995 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hosted?

The EU tag is how GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J lists itself in Europe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 185.83.154.139:28025 is the address it uses.

What build of Rust does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J use?

Rust network protocol 2635 and build 168909 on Linux is what GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

3 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 25% of its recent wipes. It fell under half by day 3 in the wipes where it didn't hold.

How often does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J wipe, and on which days?

Lately the wipes at GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J have come about every 4 days. Saturday 31 October at 14:57 UTC is when its next wipe is due. 32 hours is how long the current world has been running. In its tags it sets out a wipe schedule of every two weeks.

Tags

What do the server tags on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J mean?

The game's server browser reads the tags GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J publishes: gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): Slots: 200; ts4 (Group limit): The team limit is 4; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $rDE (Region code): Region code: DE; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here; EU (Europe): In the server browser it appears under Europe. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J appear?

These Rust Server Trends lists include GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J: 2x Rust servers, listed live, EU Rust servers and Modded Rust servers, tracked 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.

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

One operator most likely runs these: GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J and 3 other servers we track, all publishing a grub.army hostname.

Connecting

What steps get you onto GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?

You can connect by pressing F1 in Rust and typing client.connect 185.83.154.139:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://discord.com/invite/grubarmy is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp200
Max players Slots: 200.
ts4
Group limit The team limit is 4.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$rDE
Region code Region code: DE.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Unchanged from Facepunch's release: no altered rates, kits or rules.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

Region

EU
Europe In the server browser it appears 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.