Rust Server Analytics 54,249 players11,692 servers
All servers
Drill-through Server detail

Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10

Online 185.207.214.219:10000 checked 9m ago

Drill-through
FilterServeris Magic Rust #33 — Modded 2x (No limit) | B…
Attributes
2x moddedoxide
Last refreshed
Players now 44/ 200
7-day average 108 peak 393
Rank #150 top 0.7%
Last wipe 1d ago no schedule published
Next wipe 5d 8h Wed 4 Nov, 10:02 UTC
Capacity 22% full

Players

average and peak, with its wipes marked
AveragePeakWipe
010020030040002:0011:0021:0006:0015:0000:00Wiped Wed 28 Oct, 10:02 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
02040608002:0011:0021:0006:0015:0000:00Wiped Wed 28 Oct, 10:02 UTCWIPE

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
11k2k3k4k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Wipe schedule

fixed weekdays

Next wipe Wednesday 4 November, 10:02 UTC, in 5d 8h. Every Wednesday at 10:02 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak212players, last three wipes
crowd held0%else halves by day 4

Coming wipes

InWhen, UTCKind
5d 8hWed 4 Nov, 10:02 UTCits own
6d 17hThu 5 Nov, 19:00 UTCFW force wipe
12d 8hWed 11 Nov, 10:02 UTCits own
19d 8hWed 18 Nov, 10:02 UTCits own
26d 8hWed 25 Nov, 10:02 UTCits own
33d 8hWed 2 Dec, 10:02 UTCits own
34d 17hThu 3 Dec, 19:00 UTCFW force wipe
40d 8hWed 9 Dec, 10:02 UTCits own

The first 48 hours of its last wipes

Wed 21 OctWed 14 OctWed 7 Oct
0100200300400+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 236, 7 hours in, with 63 in the queue.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 10:02 UTC1d ago – – running 26
Wed 21 Oct, 10:01 UTC8d ago 236+63 queue halved by day 5 7 days 7
Wed 14 Oct, 10:02 UTC15d ago 234+41 queue halved by day 3 7 days 14
Wed 7 Oct, 10:02 UTC22d ago 167 halved by day 3 7 days 12
Wed 23 Sep, 10:01 UTC36d ago 236+56 queue halved by day 4 14 days 9
Wed 16 Sep, 10:01 UTC43d ago 235+51 queue halved by day 4 7 days 3

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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 803 on average 259 / 300
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 626 on average 676 / 700
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 356 on average 281 / 320
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 319 on average 14 / 1000
Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 305 on average 377 / 400
MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10 EU · groups of 300+ · 2x · weekly · 290 on average 49 / 1900

Quick answers

from the figures on this page

Wipe cycle

On what cycle does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 wipe?

Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 follows a wipe rhythm of every Wednesday at 10:02 UTC. Wednesday 4 November at 10:02 UTC is the date the next wipe falls on. 39 hours ago the current world was made.

On Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, what happens on wipe day?

The average busiest count over recent wipes is 212 players. With 63 more in the queue, the latest wipe peaked 7 hours after the wipe. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. The fall below half arrived by day 4 when it didn't hold.

Server

In which region does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 sit?

Without a region tag, Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 still has a name that points to Europe. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 185.207.214.219:10000 is its address.

Which Rust version is Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 on?

Rust network protocol 2635 and build 168909 on Windows is the setup for Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10. The protocol has to match before you can join; Steam updates it automatically.

Is Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 up, and how steady is its uptime?

Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 reports online at the current check. The uptime it reports puts the last restart at about 18 hours ago. Uptime over the last full days (7) was 99%, or 167 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.

Does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 perform well?

Over 48 hours the average held at 45 server fps, and the minimum was 34. Buildings, deployables and all other world objects brought the entity total to 293,691. At its highest, memory use was 8,765 MB. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

Which meanings do the tags on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 carry?

The game's server browser reads the tags Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 publishes: gmrust (Game mode): Survival in the standard Rust format; mp200 (Max players): Player slots: 200; ts50 (Group limit): Teams hold no more than 50; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play; jp2 (Custom tag): Not one of Rust's standard tags; the owner or a plugin applied it. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

On Rust Server Analytics, which lists and filters feature Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

Among the Rust Server Analytics lists Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 fits are: Rust servers with a 2x gather rate, EU Rust servers: live population data and Modded Rust servers: live data. It appears on the server list under the following filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days; Gather rate: 2x; Players now: At least 10; Average players: 100+ on average.

Who operates Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

35 other servers we track publish a magicrust.gg hostname too, and so does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, which points to a shared operator.

Player numbers

Where does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 sit among Rust servers?

Player hours for the last seven days place Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 at #150, in the top 0.7% of the ranked field.

At what level does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 run its population?

Population at the current refresh: 44 players on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, against 200 slots. Averaging 108 players across seven days, the server reached a peak of 393. The 48-hour peak window is 12:00 UTC, at an average of 383 players.

Settings

What settings and rules does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 use?

Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 names a 2x gather rate. A maximum of 50 players per group applies. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Oxide plugins are run. Anti-cheat status: VAC on.

The map on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10: which one is it?

Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 uses a procedural map of size 4,000 with seed 1337, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here. The name of the map is Baйп был 1д нaзaд.

Connection

What is the way onto Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

In the Rust console (F1), enter client.connect 185.207.214.219:10000. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://magicrust.gg/serv33 is its website.

Server tags

what each one means

Published as mp200,ptrak,jp2,$r?,v2635,gmrust,cs168909,ts50,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp200
Max players Player slots: 200.
ts50
Group limit Teams hold no more than 50.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code The region code is blank.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded The Modded section, because plugins or settings modify play.

Other

jp2
Custom tag Not one of Rust's standard tags; the owner or a plugin applied it.

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.