Online EU 185.83.154.139:28025 checked 12m ago
GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J
Connect
srv = rust.server("185.83.154.139:28027")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 18% of all ranked servers, top 49% in EU, and #253 of the quad servers (top 30%). Ranked on player hours over the last seven days.
Wipe schedule · a steady gap
srv.wipe_schedule()
Next wipe Saturday 31 October, 14:57 UTC, in 2d 12h. # Every 4 days · medium confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 2d 12h | Sat 31 Oct, 14:57 UTC | wipe |
| 1 | 6d 12h | Wed 4 Nov, 14:57 UTC | wipe |
| 2 | 7d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 3 | 10d 12h | Sun 8 Nov, 14:57 UTC | wipe |
| 4 | 14d 12h | Thu 12 Nov, 14:57 UTC | wipe |
| 5 | 18d 12h | Mon 16 Nov, 14:57 UTC | wipe |
| 6 | 22d 12h | Fri 20 Nov, 14:57 UTC | wipe |
| 7 | 26d 12h | Tue 24 Nov, 14:57 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 14:57 UTC1d ago | NaN | NaN | running | 0 |
| 1 | Fri 23 Oct, 14:58 UTC5d ago | 3 | halved by day 3 | 4 days | 1 |
| 2 | Mon 19 Oct, 14:57 UTC9d ago | 4 | held half | 4 days | 0 |
| 3 | Thu 15 Oct, 14:57 UTC13d ago | 1 | halved by day 3 | 4 days | 0 |
| 4 | Sun 11 Oct, 14:57 UTC17d ago | 0 | NaN | 4 days | 0 |
| 5 | Wed 7 Oct, 14:57 UTC21d ago | 1 | halved by day 1 | 4 days | 0 |
| 6 | Sat 3 Oct, 14:57 UTC25d ago | 2 | halved by day 1 | 4 days | 0 |
| 7 | Thu 1 Oct, 18:19 UTC FW27d ago | 2 | NaN | 1.9 days | 0 |
| 8 | Tue 29 Sep, 14:57 UTC29d ago | 3 | held half | 2.1 days | 0 |
| 9 | Fri 25 Sep, 14:57 UTC33d ago | 5 | halved by day 2 | 4 days | 0 |
| 10 | Mon 21 Sep, 19:10 UTC37d ago | 0 | NaN | 3.8 days | 0 |
| 11 | Thu 17 Sep, 14:57 UTC41d ago | 0 | NaN | 4.2 days | 0 |
| 12 | 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.
display(srv.map, srv.info())
Operator · grub.army
rust.servers(operator="grub.army").sort_values("players")
4 servers publish a grub.army hostname.
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [RU] MAALVI RUST | X2 | EU · quad · 2x · biweekly · 1 on average | 0/100 |
| 1 | Free Fields 2x | Noob Friendly | EU · quad · 2x · biweekly · 1 on average | 1/100 |
| 2 | Atlas - EU 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip | EU · quad · 2x · monthly · 564 on average | 204/250 |
| 3 | WARBANDITS.GG EU 2X |Solo/Duo/Trio/Quad|X2 JUST WIPED | EU · quad · 2x · weekly · 211 on average | 66/200 |
| 4 | EU RENEGADE 2x Monthly | Solo Duo Trio Quad | 50% Upkeep | No B | EU · quad · 2x · monthly · 145 on average | 34/150 |
| 5 | EU Limitless 2x Monthly Duo/Trio/Quad|No BP Wipes|Noob Friendly | EU · quad · 2x · monthly · 136 on average | 43/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J rank?
On seven-day player hours GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J is #3,923 overall and #1,430 in Europe, inside the top 18% of all ranked servers. Within the quad group, its rank is #253.
How many players does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hold at once?
The sample now reads 1 players for GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, out of 200 slots. Over the last seven days it averaged 1 players and peaked at 3. The 48-hour sample puts the busiest hour at 20:00 UTC, averaging 2 players.
Server facts
What does performance look like on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
The 48-hour average is 30 server fps, with a low of 30. Entity numbers reached 75,953, and that includes buildings, deployables and the rest. Memory peaked at 3,995 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J. Joining needs the same protocol on your game; Steam handles the update.
Is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J up, and what does its uptime show?
GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J reports itself online at the current refresh. A restart about 34 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hosted?
With its EU tag, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J lists itself in Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.83.154.139:28025.
Map and rules
Which rules apply on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, and what settings?
2x gather is what the name states, and the name is GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J. quad sets the cap: 4 players per group. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.
Which map has GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J selected?
Size 3,500, seed 1337: the procedural map on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe data
When does GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J wipe, and on what schedule?
About every 4 days is how often GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J has wiped of late. Saturday 31 October at 14:57 UTC is when the next wipe is due. A new world was started 35 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
On GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J, what happens on wipe day?
The average peak over recent wipes is 3 players. Peak population on the latest wipe came 1 hours in. The crowd stayed above half that peak until the next wipe in 25% of recent wipes. The drop under half arrived by day 3 in the other cases.
Tags and filters
Which Rust Data filters and lists contain GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
On Rust Data, GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J appears in these lists: EU Rust servers, Modded Rust servers and 2x Rust servers. It appears under these filters 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 operates GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J and 3 other servers we track both publish a grub.army hostname, so the same operator most likely runs them.
Which meanings do the tags on GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J hold?
Read by the game's server browser, the tags GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): Slot count: 200; ts4 (Group limit): No team may exceed 4; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $rDE (Region code): The row gives DE as its region code; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins; EU (Europe): The server browser files it under Europe. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into GRUB.ARMY EU 2X SOLO/DUO/TRIO | Raidable Bases | Shared BPs | J?
Enter client.connect 185.83.154.139:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/grubarmy is the website recorded for it.
