On the class lists: D (54), with population over 48 hours and no performance mark.
Players now1/ 2000% full
7-day average1peak 3
Rank#3,849top 17% · #1416 in EU
Last wipe1d agobiweekly schedule
Next wipe2d 7hSat 31 Oct, 14:57 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 1 of 200 on average. Plenty of space to grow.
Standingrank on player hours
83/ 100
B+
Holds a respectable place: #3,849 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
66/ 100
C+
Climbing fast: up 1,235 places this week.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 17% of all ranked servers, top 49% in EU, and #247 of the quad servers (top 30%). Ranked on player hours over the last seven days.
Attendance: the wipe record
13 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
···W···
W···W··
·W·F·W·
··W···W
···W···
W···W··
·W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Saturday 31 October, 14:57 UTC, in 2d 7h.
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
2d 7hSat 31 Oct, 14:57 UTC
6d 7hWed 4 Nov, 14:57 UTC
7d 12hThu 5 Nov, 19:00 UTCFW
10d 7hSun 8 Nov, 14:57 UTC
14d 7hThu 12 Nov, 14:57 UTC
18d 7hMon 16 Nov, 14:57 UTC
22d 7hFri 20 Nov, 14:57 UTC
26d 7hTue 24 Nov, 14:57 UTC
The first 48 hours of its last wipes
Fri 23 OctMon 19 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTCFW27d 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
Mon 21 Sep, 19:10 UTC37d ago
0
–
3.8 days
0
Thu 17 Sep, 14:57 UTC41d ago
0
–
4.2 days
0
Sun 13 Sep, 14:58 UTC45d ago
1
halved by day 3
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sit?
The EU tag on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 185.83.154.139:28025.
Is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J up, and how steady is its uptime?
Right now, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is online. About 38 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J perform well?
It never fell below 30 server fps in the last 48 hours, averaging 30. At its peak, it held 75,953 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,853 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sit?
The server GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J wipe its map?
The gap between GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J's wipes has been about 4 days recently. It is due to wipe next on Saturday 31 October at 14:57 UTC. It has been running its current world for 40 hours. Its tags give a wipe schedule of every two weeks.
What happens on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J when wipe day arrives?
Across its recent wipes, the busiest moments averaged 3 players. 1 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 25% of its recent wipes. In the other wipes it slipped under half by day 3.
Population
What position does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hold in the rankings?
In Europe, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is #1,416, and overall it is #3,849 on player hours over the last seven days, in the top 17% of all ranked servers. It comes #247 among servers in the quad group.
Is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J a busy server?
GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is showing 1 players right now, with 200 slots in total. It peaked at 3 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 20:00 UTC, averaging 2 players.
Lists and filters
What is meant by the tags on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
You'll see GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J tagged with gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 slots are available; ts4 (Group limit): No team may go above 4; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $rDE (Region code): It is filed under the region code DE; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here; EU (Europe): The server browser lists it under Europe in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who operates GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
The same operator most likely runs GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J and the 3 other servers we track that also publish a grub.army hostname.
Where does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J appear in the Rust Server Score lists and filters?
Rust Server Score lists that include GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: 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.
Server rules
How is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J set up, and what rules does it keep?
GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sets gather at 2x, as its name suggests. The cap on group size is 4 players (quad). survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J uses?
A procedural map of size 3,500 and seed 1337, generated by the game, is what GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
How to join
How do you get onto GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
To connect, start Rust, press F1, and type client.connect 185.83.154.139:28025. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://discord.com/invite/grubarmy.
Server tags
what each one means
Published asmp200,ptrak,$rDE,v2635,^z,^y,^b,^v,EU,gmvanilla,cs168909,ts4
Game
gmvanilla
Game modeThis is vanilla survival.
mp200
Max players200 slots are available.
ts4
Group limitNo team may go above 4.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rDE
Region codeIt is filed under the region code DE.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
Region
EU
EuropeThe server browser lists 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).