RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,329 Populated2,867 Fresh wipes 3 h54 Scan5 min
‹ All servers185.149.40.74:28015
Online Full Queue Fresh wipe Wipe due No query

Void.Place | x2

Online EU 185.149.40.74:28015 checked 13m ago

2x weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 02:00 UTC
0 75 150 225 300 PAX 0 /300

Players now

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

Server fps

48 h low 109 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 107,384 ×1000

Entities

48 h range 106,918–109,576 · memory 5,905 MB
1239 ET SINCE RESTART 5D 08H

Uptime

5 days 8 hours since its last restart, at the last reading
7-day average0peak 3
Rank#7,216top 32% · #2019 in EU
Last wipe5d agoweekly schedule
Next wipe1d 14hThu 29 Oct, 18:10 UTC
Memory5,905MBat the last reading
REC 1

Players

AveragePeak
0123404:0013:0022:0008:0017:0002:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020004:0013:0022:0008:0017:0002: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 29 October, 18:10 UTC, in 1d 14h. Every Thursday at 18:10 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held40%else halves by day 3

Coming wipes

  1. WPT 1Thu 29 Oct, 18:10 UTC1d 14h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 15hFW
  3. WPT 3Thu 12 Nov, 18:10 UTC15d 14h
  4. WPT 4Thu 19 Nov, 18:10 UTC22d 14h
  5. WPT 5Thu 26 Nov, 18:10 UTC29d 14h
  6. WPT 6Thu 3 Dec, 19:00 UTC36d 15hFW
  7. WPT 7Thu 10 Dec, 18:10 UTC43d 14h

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 18:10 UTC5d ago 3 – running 3
Thu 15 Oct, 17:58 UTC12d ago 2 held half 7 days 0
Thu 8 Oct, 17:58 UTC19d ago 3 halved by day 5 7 days 0
Thu 1 Oct, 18:19 UTC FW26d ago 5 halved by day 3 7 days 0
Thu 24 Sep, 18:19 UTC33d ago 11 halved by day 2 7 days 1
Thu 17 Sep, 18:04 UTC40d ago 2 held half 7 days 0

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 Void.Place | x2 when wipe day comes?

An average of 3 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 40% of its recent wipes. When it didn't hold, by day 3 it fell below half.

What wipe timing does Void.Place | x2 follow?

The wipe rhythm of Void.Place | x2 is every Thursday at 18:10 UTC. Due on Thursday 29 October at 18:10 UTC is its next wipe. The world it runs now was made 5 days 9 hours ago. The tags state a wipe schedule of one wipe a week.

Tags

How should you read the tags on Void.Place | x2?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp300 (Max players): Slots: 300; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): Its browser listing: Europe from Void.Place | x2. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Void.Place | x2?

Rust Metrics lists featuring Void.Place | x2: 2x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.

Player count

Where does Void.Place | x2 sit in the rankings?

Player hours over the last seven days put Void.Place | x2 at #7,216, #2,019 in Europe, in the top 32% of all ranked servers.

What player count does Void.Place | x2 carry?

Current headcount on Void.Place | x2: 0 players, 300 slots available. Check: players over seven days. Average 0, peak 3.

Server

What location is Void.Place | x2 hosted in?

Reading: location. The EU tag puts Void.Place | x2 in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.149.40.74:28015.

What Rust version is Void.Place | x2 on?

Rust network protocol 2634 and build 168909 on Linux is the build Void.Place | x2 runs. Check: protocol. To join, your game must match; Steam handles the update.

How does Void.Place | x2 perform?

Over the last 48 hours the average was 138 server fps; the floor was 109. Peak entity count: 109,576. Buildings, deployables and all else included. Reading: 5,909 MB of memory at the highest. Expect lag when fps falls and entities climb.

What is the uptime on Void.Place | x2, and is it online?

Check: connection. Void.Place | x2 is online at this moment. By its reported uptime, the last restart was roughly 5 days 8 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Void.Place | x2?

The name carries the rate: 2x gather on Void.Place | x2. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on Void.Place | x2?

Size 4,500 and seed 1155742565: the game generates the procedural map on Void.Place | x2 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

How do you connect to Void.Place | x2?

Press F1 in Rust and enter client.connect 185.149.40.74:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://void.place/.

PLACARDS

Server tags

what each one means

Published as mp300,ptrak,$r?,v2634,^w,EU,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp300
Max players Slots: 300.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EU
Europe Its browser listing: 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.