Rust Data

rustdata.spaceservers51.81.179.74:28163.ipynb

Run all rust-data · live

‹ All servers

Online 51.81.179.74:28162 checked 9m ago

Grubber Rust | 2x Bi-Weekly

2x moddedoxide

Connect

srv = rust.server("51.81.179.74:28163")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 7
rank #4,630 # top 21%
last wipe 6d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040019:0004:0013:0023:0008:0017: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 16 Oct. 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
RankRank in region
12.5k5k7.5k10k16 Oct19 Oct21 Oct24 Oct26 Oct29 Oct

Top 21% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak7players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 17:25 UTC6d ago 7 NaN running 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())

Map

2700 · seed 847294
Map of Grubber Rust | 2x Bi-Weekly
map
Procedural Map
size
2700
seed
847294
Open on RustMaps

Server

srv.info()
address
51.81.179.74:28162
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
23 Oct 2026, 17:25 UTC
hostname
–
first seen
16 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 832 on average717/800
1Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 610 on average1580/1600
2Atlas - US 2X Monthly | Vanilla+ | No BP WipesNA · groups of 16+ · 2x · monthly · 379 on average155/200
3EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 348 on average818/850
4Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 333 on average801/900
5MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 317 on average125/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Grubber Rust | 2x Bi-Weekly rank?

Rank #4,630 on seven-day player hours for Grubber Rust | 2x Bi-Weekly, within the top 21% of all ranked servers.

What population does Grubber Rust | 2x Bi-Weekly carry?

The sample now reads 0 players for Grubber Rust | 2x Bi-Weekly, out of 40 slots. Over the last seven days it averaged 0 players and peaked at 7.

About the server

What does performance look like on Grubber Rust | 2x Bi-Weekly?

The 48-hour average is 225 server fps, with a low of 203. Buildings, deployables and all else in the world took the count as high as 37,211 entities. The memory field tops out at 5,540 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Grubber Rust | 2x Bi-Weekly run?

Rust network protocol 2635 and build 168909 on Linux is what Grubber Rust | 2x Bi-Weekly runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Grubber Rust | 2x Bi-Weekly, and is it up?

Online is the state at the latest refresh for Grubber Rust | 2x Bi-Weekly. 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 16 October 2026.

Which location does Grubber Rust | 2x Bi-Weekly run from?

For Grubber Rust | 2x Bi-Weekly, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 51.81.179.74:28162.

Rules, settings, map

What rules and settings are recorded for Grubber Rust | 2x Bi-Weekly?

Gather sits at 2x, read from the server's own name: Grubber Rust | 2x Bi-Weekly. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has Grubber Rust | 2x Bi-Weekly loaded?

Size 2,700, seed 847294: the procedural map on Grubber Rust | 2x Bi-Weekly, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does Grubber Rust | 2x Bi-Weekly wipe, and how often?

A rhythm cannot be read from the wipes of Grubber Rust | 2x Bi-Weekly on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 6 days 1 hours ago.

What is wipe day on Grubber Rust | 2x Bi-Weekly like?

Across recent wipes the busiest point averaged 7 players. The crowd on the latest wipe topped out 4 hours after it began.

Tags, lists

Which lists on Rust Data hold Grubber Rust | 2x Bi-Weekly, and which filters?

On Rust Data, Grubber Rust | 2x Bi-Weekly appears in these lists: Modded Rust servers and 2x Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.

Which meanings do the tags on Grubber Rust | 2x Bi-Weekly hold?

These tags are published by Grubber Rust | 2x Bi-Weekly and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to Grubber Rust | 2x Bi-Weekly?

The manual route: launch Rust, F1, then client.connect 51.81.179.74:28162. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players Slot count: 40.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 104,075 players 11,902 servers online