StatusLive Servers online11,706 Players60,014 Populated3,275 Wiped · 3 h169 Interval5 min Date30 OCT 2026

DWG RG-S0152Server sheetchecked 14m ago

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

Online 185.207.214.219:10000 checked 14m ago

2x moddedoxide
Connect
Players now 51/ 200 26% full
7-day average108peak 393
Rank#152top 0.7%
Last wipe1d agono schedule published
Next wipe5d 9hWed 4 Nov, 10:02 UTC
Fig. 1

Players

AveragePeakWipe
010020030040001:0010:0020:0005:0014:0023:00Wiped Wed 28 Oct, 10:02 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10
Fig. 2

Server performance

Server fpsWipe
02040608001:0010:0020:0005:0014:0023: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

fixed weekdays

Next wipe Wednesday 4 November, 10:02 UTC, in 5d 9h. 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

  1. 5d 9hWed 4 Nov, 10:02 UTC
  2. 6d 18hThu 5 Nov, 19:00 UTCFW
  3. 12d 9hWed 11 Nov, 10:02 UTC
  4. 19d 9hWed 18 Nov, 10:02 UTC
  5. 26d 9hWed 25 Nov, 10:02 UTC
  6. 33d 9hWed 2 Dec, 10:02 UTC
  7. 34d 18hThu 3 Dec, 19:00 UTCFW
  8. 40d 9hWed 9 Dec, 10:02 UTC

The first 48 hours of its last wipes

Wed 21 OctWed 14 OctWed 7 Oct
0100200300400+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 805 on average
298 / 350
02
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 624 on average
783 / 825
03
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 355 on average
353 / 395
04
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 319 on average
19 / 1000
05
Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 303 on average
425 / 500
06
MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10EU · groups of 300+ · 2x · weekly · 290 on average
66 / 1900
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

How reliable is Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, and is it online now?

At this moment Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 is online. The uptime it reports puts the last restart at about 17 hours ago. For the last 7 full days the record is 143 of 168 hours up, 85% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 stable in the figures recorded?

Average server fps over the last 48 hours is 45; the lowest was 34. Counted at its highest: 293,691 entities, buildings, deployables and the rest of the world included. Memory use peaked at 8,765 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

No region tag is published by Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, but its name points to Europe. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 185.207.214.219:10000.

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

Rust network protocol 2635 and build 168909 on Windows: that is what Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 runs. The same protocol is required for joining, and Steam updates your game to it.

Player data

How many players are plotted on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

51 of 200 slots on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 are taken at the latest refresh. Averaged across seven days, the player count is 108, with a peak of 393. Averaged over the last 48 hours, the player count is highest at 12:00 UTC: 383 players.

In the rankings, which position does Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 hold?

Player hours over seven days place Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 at #152, within the top 0.7% of ranked servers.

Wipe times

What happens on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 on the day of a wipe?

An average of 212 players was recorded at the busiest point of its recent wipes. 7 hours after the latest wipe the crowd peaked, with 63 further players waiting in the queue. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 4.

On Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10, when do wipes occur?

The wipe rhythm at Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 is every Wednesday at 10:02 UTC. On Wednesday 4 November at 10:02 UTC its next wipe is due. 38 hours ago the current world was made.

Map and rules

Which rules and settings are recorded for Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

2x gather is stated in the name of Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10. 50 players is the published group limit. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.

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

Seed 1337 and size 4,000 define the procedural map Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. Recorded map name: Baйп был 1д нaзaд.

Filters

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

On Rust Graphs, Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 is placed in these lists: Servers with a 2x gather rate, Europe servers, plotted and Modded Rust servers. These filters on the server list return it: 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 50; Average players: 100+ on average.

Which meaning is attached to each tag on Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

gmrust (Game mode): Survival in standard Rust style; mp200 (Max players): The slot count is 200; ts50 (Group limit): Teams hold no more than 50; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; jp1 (Custom tag): Set by the owner or a plugin, not by standard Rust are the tags Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

By whom is Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 run?

The same operator most likely runs Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10 and 35 other servers we track, since all publish a magicrust.gg hostname.

How to join

By what method do you join Magic Rust #33 — Modded 2x (No limit) | Baйп 28.10?

In Rust, press F1 and type client.connect 185.207.214.219:10000 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://magicrust.gg/serv33.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp200
Max players The slot count is 200.
ts50
Group limit Teams hold no more than 50.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Other

jp1
Custom tag Set by the owner or a plugin, not by standard Rust.

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.

KeyTag string decoded