StatusLive Servers online11,892 Players102,135 Populated3,937 Wiped · 3 h401 Interval5 min Date29 OCT 2026

DWG RG-S2868Server sheetchecked 13m ago

#2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10

Online EU 37.230.210.93:20610 checked 13m ago

1e+06x weekly wipes moddedoxide
Connect
Players now 5/ 200 2% full
7-day average1peak 7
Rank#2,868top 13% · #1083 in EU
Last wipe6h agoweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeakWipe
0246818:0003:0012:0022:0007:0016:00Wiped Thu 29 Oct, 11:09 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on #2 RAIDCORE X1000000 | FPS++ | TP | KIT |...
Fig. 2

Server performance

Server fpsWipe
02040608018:0003:0012:0022:0007:0016:00Wiped Thu 29 Oct, 11:09 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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 13% of all ranked servers, top 37% in EU. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. The force wipe · high confidence

usual gap7 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak6players, last three wipes
crowd held50%else halves by day 2.5

Coming wipes

  1. 7d 1hThu 5 Nov, 19:00 UTCFW
  2. 13d 17hThu 12 Nov, 11:09 UTC
  3. 20d 17hThu 19 Nov, 11:09 UTC
  4. 27d 17hThu 26 Nov, 11:09 UTC
  5. 35d 1hThu 3 Dec, 19:00 UTCFW
  6. 41d 17hThu 10 Dec, 11:09 UTC

The first 48 hours of its last wipes

Thu 22 OctThu 15 OctThu 8 Oct
02468+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 7, 44 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 11:09 UTC6h ago – – running 3
Thu 22 Oct, 11:10 UTC7d ago 7 – – 0
Thu 15 Oct, 11:10 UTC14d ago 4 held half 7 days 1
Thu 8 Oct, 19:35 UTC20d ago 6 halved by day 1 6.6 days 0
Fri 2 Oct, 08:48 UTC27d ago 5 held half 6.4 days 0
Thu 1 Oct, 11:09 UTC28d ago 3 – 0.9 days 1
Thu 24 Sep, 11:09 UTC35d ago 3 held half 7 days 0
Thu 17 Sep, 11:10 UTC42d ago 7 halved by day 5 7 days 1

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
MelonRust.ru #2 X1000000 [NOLIM | FPS+ | BF | BARREN]EU · groups of 8+ · 1e+06x · weekly · 105 on average
173 / 300
02
TMKBUD X1000000 | HARDPVP | BATTLEFIELD | CLANS | NOLIMIT | FPSEU · groups of 99+ · 1e+06x · weekly · 27 on average
68 / 200
03
[EU] SLAYERS.GG Battlefield Million X1000000 PVP|SKIN|SCRAP|KITEU · groups of 12+ · 1e+06x · weekly · 2 on average
4 / 100
04
BAIDEN RUST X1000000000 |NoLimit|PVP|FUN|KITS|RU|EU|AIM|BED|BROEU · groups of 100+ · 1e+09x · weekly · 36 on average
74 / 200
05
ICE RUST #1 - X1000 [ KITS | LOOT+ | FPS+ | BF | NOLIM | 1000x]EU · groups of 24+ · 1000x · weekly · 31 on average
48 / 200
06
[EU] ICEFUSE BATTLEFIELD x1000000000|MYMINI|CLANS|KITS|PVP|FPSEU · groups of 100+ · 1e+09x · weekly · 18 on average
34 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 online, and what uptime has been recorded?

At this moment #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 is online. The uptime it reports puts the last restart at about 4 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

How does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 perform, as measured?

57 server fps on average over the last 48 hours, and never under 1. Counted at its highest: 72,466 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 4,551 MB. What players feel as lag is low fps together with a climbing entity count.

In which location is #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 hosted?

With its EU tag, #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 lists itself in Europe. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 37.230.210.93:20610 is its address.

What Rust version is recorded for #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10. To join, your game must be on the same protocol; Steam handles the update.

Player data

What does the population history show for #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

5 of 200 slots on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 are taken at the latest refresh. The seven-day mean is 1 players; the peak over the same period is 7. Averaged over the last 48 hours, the player count is highest at 19:00 UTC: 5 players.

In the rankings, which position does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 hold?

Across seven days, player hours give #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 #2,868 globally and #1,083 in Europe, a top 13% position among ranked servers.

Wipe times

On #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10, what does the data show for wipe day?

An average of 6 players was recorded at the busiest point of its recent wipes. At 44 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 50% of its recent wipes. By day 2.5 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

Wipes at #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 take place every Thursday at 11:09 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 6 hours ago. A wipe every week is the schedule its tags set out.

Settings

Which settings does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 run, and what rules?

1e+06x gather is stated in the name of #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10. 50 players is the published group limit. It runs the combat training game mode, aim and PvP practice, loot handed out. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

What is the map for #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

Seed 1282240169 and size 3,500 define the procedural map #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 appear among the Rust Graphs lists and filters?

On Rust Graphs, #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10 is placed in these lists: Rust servers above 10x gather rate, Europe servers, plotted, Modded Rust servers, Rust aim training servers, listed live and Rust battlefield servers. It is returned by these filters on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Combat training ^d, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: More than 10x.

Which meaning is attached to each tag on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

The game's server browser reads these tags from #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10: gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 player slots; ts50 (Group limit): Team size is capped at 50; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^w (Weekly): A wipe occurs every week; ^d (Combat training): Loot comes free, for aim and PvP practice; ^i (Battlefield): High rates and kits make for fast PvP; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; EU (Europe): The browser's listing places it under Europe. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

By what method do you join #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP29.10?

Enter client.connect 37.230.210.93:20610 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://darkness-rust.ru is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^w,^d,^i,EU,gmvanilla,cs168909,ts50,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp200
Max players 200 player slots.
ts50
Group limit Team size is capped at 50.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^w
Weekly A wipe occurs every week.

Gameplay

^d
Combat training Loot comes free, for aim and PvP practice.
^i
Battlefield High rates and kits make for fast PvP.

Mods and access

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

Region

EU
Europe The browser's listing places it under Europe.

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