On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ 2000% full
7-day average0peak 4
Rank#4,956top 22% · #1688 in EU
Last wipe2d agobiweekly schedule
Next wipe8d 10hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
78/ 100
B
Holds a respectable place: #4,956 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 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
60/ 100
C
Keeps a fair share of its players through a wipe: 60% of wipes kept half their crowd.
Momentumrank now against a week ago
45/ 100
D
Slipped a little: down 527 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 22% of all ranked servers, top 58% in EU, and #312 of the quad servers (top 38%). Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W···W·
··W···W
···F···
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
fixed weekdays
Next wipe Thursday 5 November, 19:00 UTC, in 8d 10h.
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
8d 10hThu 5 Nov, 19:00 UTCFW
13d 6hTue 10 Nov, 14:57 UTC
17d 6hSat 14 Nov, 14:57 UTC
21d 6hWed 18 Nov, 14:57 UTC
25d 6hSun 22 Nov, 14:57 UTC
36d 10hThu 3 Dec, 19:00 UTCFW
41d 6hTue 8 Dec, 14:57 UTC
The first 48 hours of its last wipes
Sun 25 OctWed 21 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 14:57 UTC2d ago
2
–
running
0
Wed 21 Oct, 14:57 UTC6d ago
2
✓ held half
4 days
0
Sat 17 Oct, 14:57 UTC10d ago
3
halved by day 2
4 days
0
Tue 13 Oct, 14:57 UTC14d ago
3
✓ held half
4 days
0
Fri 9 Oct, 14:57 UTC18d ago
3
halved by day 1
4 days
0
Mon 5 Oct, 14:57 UTC22d ago
3
✓ held half
4 days
0
Thu 1 Oct, 19:25 UTCFW26d ago
5
✓ held half
3.8 days
1
Sun 27 Sep, 14:57 UTC30d ago
3
✓ held half
4.2 days
0
Wed 23 Sep, 14:57 UTC34d ago
1
halved by day 3
4 days
0
Sat 19 Sep, 14:57 UTC38d ago
2
✓ held half
4 days
0
Tue 15 Sep, 14:58 UTC42d ago
2
✓ held half
4 days
2
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 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sit?
In Europe, according to its own listing, sits GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, with the EU tag. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.83.154.140:28025 is the address to use.
Is GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J up, and how steady is its uptime?
You can join now: GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is online. According to its reported uptime, the last restart was about 2 days 16 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J run?
It averaged 30 server fps over the last 48 hours, with a low of 30. Buildings, deployables and everything else in the world added up to as many as 82,205 entities. At its highest, it used 3,972 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J sit?
Rust network protocol 2635 and build 168909 on Linux is what GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J reset?
Wipes come every 4 weeks on Tuesday, Wednesday, Saturday and Sunday at 14:57 UTC on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 2 days 17 hours. A fortnightly wipe schedule appears in its tags.
What happens on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J when wipe day arrives?
The average peak on its recent wipes was 2 players. The crowd on the latest wipe was largest 2 hours after it began. Above half the peak until the next wipe: that was the pattern in 60% of its recent wipes. In the other wipes it slipped under half by day 1.5.
Player count
Where does GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J place in the wider field of Rust servers?
Over the last seven days, GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J has #4,956 for player hours, in the top 22% of all ranked servers and #1,688 in Europe. It comes #312 among servers in the quad group.
What does the population on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J look like?
Right now, 0 players are on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, which has 200 slots. The seven-day average is 0 players, with a peak of 4. Over the last 48 hours, the peak hour was 19:00 UTC, averaging 3 players.
Tags
How should you read the tags on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
You'll see GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J tagged with gmvanilla (Game mode): You play vanilla survival here; mp200 (Max players): Its slot count is 200; ts4 (Group limit): A team can hold 4 players at most; 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): This is RakNet: the network layer Rust normally uses; $rDE (Region code): DE is the region code this server uses; ^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): The plugin framework in use is Carbon; EU (Europe): In the server browser it appears under Europe in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which person or group runs GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
3 other servers we track also use a grub.army hostname, so they and GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J most likely share an operator.
Which lists and filters on Rust Server Score show GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
Rust Server Score lists that include GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J: 3x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. 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: 3x.
Rules and settings
How is GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J set up, and what rules does it keep?
The name of GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J points to a 3x gather rate. You can have up to 4 players in a group (quad). It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Which map is in play on GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J runs a game-generated procedural map at size 3,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
How to join
What is the way to join GRUB.ARMY EU 3X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
To connect, start Rust, press F1, and type client.connect 185.83.154.140:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$rDE,v2635,^z,^y,^b,^v,EU,gmvanilla,cs168909,ts4
Game
gmvanilla
Game modeYou play vanilla survival here.
mp200
Max playersIts slot count is 200.
ts4
Group limitA team can hold 4 players at most.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rDE
Region codeDE is the region code this server uses.
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
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeIn 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.
A fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).