Rust Server TrendsSeismic network · station log
Recording Stations11,625 Players41,682 Active3,017 Wipes · 3 h84 48 h

Station XX-15338 · recording

BudGame MAX 3 | Loot+ | Custom

Online 45.11.16.75:28530 checked 10m ago

moddedcarbon
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,338
top 69%
Last wipe
16d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15338 · CH Z

The last 48 hours, hour by hour

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

Players

AveragePeak
0123409:0018:0003:0011:0021:0006:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040009:0018:0003:0011:0021:0006: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 7 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
15k10k15k20k7 Oct11 Oct16 Oct20 Oct25 Oct29 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
0.8 daysbetween real wipes
on rhythm
40%of its recent wipes
wipe-day peak
3players, last three wipes

The first 48 hours of its last wipes

Mon 12 OctSun 11 OctSun 11 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 22 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 12 Oct, 16:49 UTC16d ago M0.0rising 3 – running 2
Sun 11 Oct, 20:40 UTC17d ago M0.5rising 3 – 0.8 days 0
Sun 11 Oct, 12:45 UTC17d ago M0.5rising 3 – 0.3 days 0
Fri 9 Oct, 21:09 UTC19d ago M0.3rising 2 – 1.6 days 0
Thu 8 Oct, 12:30 UTC20d ago M0.3rising 2 – 1.4 days 0
Wed 7 Oct, 16:54 UTC21d ago M0.3rising 2 – 0.8 days 0

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
ShockRust | Blue | NoLimit no group limit · 150 on average
99/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
118/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
44/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
4/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
20/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on BudGame MAX 3 | Loot+ | Custom?

The procedural map on BudGame MAX 3 | Loot+ | Custom is size 4,000 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. Its map carries the name Custom Map.

Which settings and rules apply on BudGame MAX 3 | Loot+ | Custom?

You will find no gather rate in the name of BudGame MAX 3 | Loot+ | Custom. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on BudGame MAX 3 | Loot+ | Custom right now?

At this moment, BudGame MAX 3 | Loot+ | Custom records 0 players across 100 slots. The population averaged 0 players over the past week.

How does BudGame MAX 3 | Loot+ | Custom rank against other Rust servers?

The last seven days of player hours place BudGame MAX 3 | Loot+ | Custom at #15,338, in the top 69% of all ranked servers.

Server details

How reliably does BudGame MAX 3 | Loot+ | Custom stay online?

Right now, you can reach BudGame MAX 3 | Loot+ | Custom. The uptime it reports puts its last restart about 10 days 14 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. 7 October 2026 is when Rust Server Trends first recorded it.

How well does BudGame MAX 3 | Loot+ | Custom perform under load?

Its average server fps over the last 48 hours was 134, and it never dropped below 13. At its highest, it carried 61,231 entities: buildings, deployables and the world's other contents. It reached a ceiling of 3,129 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does BudGame MAX 3 | Loot+ | Custom run from?

No region is published by BudGame MAX 3 | Loot+ | Custom. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 45.11.16.75:28530.

What build of Rust does BudGame MAX 3 | Loot+ | Custom use?

BudGame MAX 3 | Loot+ | Custom is running Rust network protocol 2634 and build 167781 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on BudGame MAX 3 | Loot+ | Custom?

The recent wipes averaged a busiest count of 3 players. The peak on the most recent wipe came 22 hours after the wipe.

How often does BudGame MAX 3 | Loot+ | Custom wipe, and on which days?

There is no next wipe to predict at BudGame MAX 3 | Loot+ | Custom, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 16 days 14 hours is how long the current world has been running.

Server tags

What do the server tags on BudGame MAX 3 | Loot+ | Custom mean?

The game's server browser reads the tags BudGame MAX 3 | Loot+ | Custom publishes: gmvanilla (Game mode): Survival in vanilla mode; mp100 (Max players): The server has 100 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^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 BudGame MAX 3 | Loot+ | Custom appear?

The Rust Server Trends lists that take in BudGame MAX 3 | Loot+ | Custom are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Join the server

How do you connect to BudGame MAX 3 | Loot+ | Custom?

You can connect by pressing F1 in Rust and typing client.connect 45.11.16.75:28530 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^z,^y

Game

gmvanilla
Game mode Survival in vanilla mode.
mp100
Max players The server has 100 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build It runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

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.