RUST METRICSFlight deck · live data
Data live Servers11,876 Players95,829 Populated4,104 Fresh wipes 3 h153 Scan5 min
‹ All servers37.230.210.93:20610
Online Full Queue Fresh wipe Wipe due No query

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

Online EU 37.230.210.93:20610 checked 14m ago

1e+06x weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Tue 17:00 UTC
0 50 100 150 200 PAX 1 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 54 SERVER FPS

Server fps

48 h low 46 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 72,476 ×1000

Entities

48 h range 70,007–73,387 · memory 3,880 MB
1239 ET SINCE RESTART 4D 05H

Uptime

4 days 5 hours since its last restart, at the last reading
7-day average1peak 7
Rank#2,890top 13% · #1092 in EU
Last wipe5d agoweekly schedule
Next wipe1d 7hThu 29 Oct, 02:46 UTC
Memory3,880MB48 h peak 4 players
REC 1

Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608019:0004:0013:0023:0008:0017: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

PLAN

Wipe schedule

a steady gap

Next wipe Thursday 29 October, 02:46 UTC, in 1d 7h. Every 6 days 16 hours · medium confidence

usual gap6.8 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak6players, last three wipes
crowd held75%else halves by day 1

Coming wipes

  1. WPT 1Thu 29 Oct, 02:46 UTC1d 7h
  2. WPT 2Wed 4 Nov, 18:22 UTC7d 23h
  3. WPT 3Thu 5 Nov, 19:00 UTC9d 0hFW
  4. WPT 4Wed 11 Nov, 09:57 UTC14d 15h
  5. WPT 5Wed 18 Nov, 01:33 UTC21d 6h
  6. WPT 6Tue 24 Nov, 17:09 UTC27d 22h
  7. WPT 7Tue 1 Dec, 08:45 UTC34d 13h
  8. WPT 8Thu 3 Dec, 19:00 UTC37d 0hFW

The first 48 hours of its last wipes

Thu 22 OctThu 15 OctThu 8 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 44 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 11:10 UTC5d ago 7 – running 0
Thu 15 Oct, 11:10 UTC12d ago 4 held half 7 days 1
Thu 8 Oct, 19:35 UTC18d ago 6 halved by day 1 6.6 days 0
Fri 2 Oct, 08:48 UTC25d ago 5 held half 6.4 days 0
Thu 1 Oct, 11:09 UTC26d ago 3 – 0.9 days 1
Thu 24 Sep, 11:09 UTC33d ago 3 held half 7 days 0
Thu 17 Sep, 11:10 UTC40d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 when wipe day comes?

An average of 6 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 44 hours. The crowd stayed above half that peak until the next wipe in 75% of its recent wipes. It fell below half by day 1 when it didn't.

What wipe timing does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 follow?

About every 6.8 days is how often #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 has wiped lately. On Thursday 29 October at 02:46 UTC its next wipe is due. The world in play was created 5 days 7 hours ago. The tags state a wipe schedule of one wipe a week.

Tag meanings

Which tags does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 carry, and what do they mean?

These are the tags #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): Slots: 200; ts50 (Group limit): Teams are capped at 50; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Check: wipe cycle. Every week; ^d (Combat training): Loot is handed to you on this training server for aim and PvP work; ^i (Battlefield): Check: mode. Battlefield, with kits and high rates for quick fights; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; EU (Europe): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 appear in Rust Metrics lists and filters?

On Rust Metrics, #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 sits in these lists: Gather rate above 10x: server list, EU Rust servers, checked, Modded Rust servers, checked live, Aim training servers, live readings and Rust battlefield servers: check the readings. Check: filters. On the server list it appears under these: 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 week; Gather rate: More than 10x.

Player count

Where does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 sit in the rankings?

Player hours over the last seven days put #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 at #2,890, #1,092 in Europe, in the top 13% of all ranked servers.

How full does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 get?

Current headcount on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10: 1 players, 200 slots available. Check: players over seven days. Average 1, peak 7. Check: 48-hour peak. 19:00 UTC, 2 players on average.

Operator and location

Where does #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 sit?

#2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 gives Europe as its location, with the EU tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 37.230.210.93:20610.

What Rust version is #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 on?

Reading: #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 within range?

Reading: 58 server fps on average across the last 48 hours. It never dropped below 46. Peak entity count: 73,387. Buildings, deployables and all else included. Check: memory. Peak use was 4,379 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 up, and how often does it stay up?

Reading: online. #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 answers right now. Check: restart. The uptime it reports puts the last restart about 4 days 5 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10?

Gather rate check: 1e+06x. That comes from the name #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10. The cap on groups is 50 players. combat training, practice for aim and PvP, loot provided — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10 on?

From seed 2038982780, the game generates the procedural map on #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10. Its size is 3,500. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How can you get onto #2 RAIDCORE X1000000 | FPS++ | TP | KIT | HOME | WP22.10?

To join: start Rust, press F1 and type client.connect 37.230.210.93:20610. Or press Launch Rust here and Steam opens the game and connects you. https://darkness-rust.ru is where its website sits.

PLACARDS

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 The mode is vanilla survival.
mp200
Max players Slots: 200.
ts50
Group limit Teams are capped at 50.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Gameplay

^d
Combat training Loot is handed to you on this training server for aim and PvP work.
^i
Battlefield Check: mode. Battlefield, with kits and high rates for quick fights.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EU
Europe The server browser files 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.