Rust Server TrendsSeismic network · station log
Recording Stations11,889 Players101,018 Active3,946 Wipes · 3 h400 48 h

Station XX-15183 · recording

BigBert's 2X [Solo/Duo/Trio] (Midwest)

Online 216.82.5.222:28015 checked 9m ago

2x moddedcarbon
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#15,183
top 68%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15183 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040018:0003:0012:0022:0007:0016: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 24 Oct. 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
15k10k15k20k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 838 on average
808/ 900
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 614 on average
1086/ 525
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 378 on average
159/ 200
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 348 on average
832/ 750
Magic Rust #18 — Vanilla 2x | Baйп 28.10 EU · groups of 150+ · 2x · weekly · 333 on average
898/ 960
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 317 on average
156/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on BigBert's 2X [Solo/Duo/Trio] (Midwest)?

BigBert's 2X [Solo/Duo/Trio] (Midwest) runs a procedural map of size 4,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.

Which settings and rules apply on BigBert's 2X [Solo/Duo/Trio] (Midwest)?

2x gather is what BigBert's 2X [Solo/Duo/Trio] (Midwest) runs, judging by its name. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on BigBert's 2X [Solo/Duo/Trio] (Midwest) right now?

A reading taken now shows 0 players on BigBert's 2X [Solo/Duo/Trio] (Midwest), which has 50 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does BigBert's 2X [Solo/Duo/Trio] (Midwest) rank against other Rust servers?

Over the last seven days, BigBert's 2X [Solo/Duo/Trio] (Midwest) recorded enough player hours to reach #15,183 worldwide, placing it in the top 68% of all ranked servers.

Server facts

How reliably does BigBert's 2X [Solo/Duo/Trio] (Midwest) stay online?

BigBert's 2X [Solo/Duo/Trio] (Midwest) is up at the moment. Its reported uptime points to a restart about 5 days 12 hours ago. 95 of 96 hours in the last 4 full days were up time, 99% of the total. On 24 October 2026 it was recorded for the first time by Rust Server Trends.

Does BigBert's 2X [Solo/Duo/Trio] (Midwest) hold a steady tick rate?

Across the last 48 hours it averaged 199 server fps, with a floor of 131. At its highest, it carried 121,321 entities: buildings, deployables and the world's other contents. Memory use peaked at 5,071 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does BigBert's 2X [Solo/Duo/Trio] (Midwest) run from?

Nothing about a region comes from BigBert's 2X [Solo/Duo/Trio] (Midwest). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 216.82.5.222:28015.

What build of Rust does BigBert's 2X [Solo/Duo/Trio] (Midwest) use?

Rust network protocol 2635 and build 168909 on Linux is what BigBert's 2X [Solo/Duo/Trio] (Midwest) runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does BigBert's 2X [Solo/Duo/Trio] (Midwest) run its wipes?

The rhythm of BigBert's 2X [Solo/Duo/Trio] (Midwest) cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 27 days 1 hours is how long the current world has been running.

Lists and tags

What do the server tags on BigBert's 2X [Solo/Duo/Trio] (Midwest) mean?

These are the tags BigBert's 2X [Solo/Duo/Trio] (Midwest) publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does BigBert's 2X [Solo/Duo/Trio] (Midwest) appear?

You will find BigBert's 2X [Solo/Duo/Trio] (Midwest) on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.

Connecting

How do you connect to BigBert's 2X [Solo/Duo/Trio] (Midwest)?

To join, enter client.connect 216.82.5.222:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.

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.