RUST METRICSFlight deck · live data
Data live Servers11,777 Players67,749 Populated3,536 Fresh wipes 3 h194 Scan5 min
‹ All servers110.235.108.197:28015
Online Full Queue Fresh wipe Wipe due No query

Distorted - PVE 3X - Events and Raidable Bases - Biweekly

Online EA 110.235.108.197:28015 checked 12m ago

3x biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 50 100 150 200 PAX 8 /200

Players now

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

Server fps

48 h low 138 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 156,305 ×1000

Entities

48 h range 137,444–159,026 · memory 3,829 MB
1239 ET SINCE RESTART 04:00

Uptime

4 h 0 min since its last restart, at the last reading
7-day average6peak 24
Rank#1,234top 6% · #125 in EA
Last wipe13d agobiweekly schedule
Next wipe1hThu 29 Oct, 14:38 UTC
Memory3,829MB48 h peak 17 players
REC 1

Players

AveragePeak
0510152013:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040013:0022:0007:0016:0002:0011: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
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 6% of all ranked servers, top 23% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 14:38 UTC, in 1h. Its biweekly schedule tag · low confidence

usual gap13.8 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak18players, last three wipes
crowd held50%else halves by day 8

Coming wipes

  1. WPT 1Thu 29 Oct, 14:38 UTC1h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 6hFW
  3. WPT 3Thu 12 Nov, 14:38 UTC14d 1h
  4. WPT 4Thu 26 Nov, 14:38 UTC28d 1h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 6hFW
  6. WPT 6Thu 10 Dec, 14:38 UTC42d 1h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctFri 18 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 23, 46 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:38 UTC13d ago 23 – running 7
Thu 1 Oct, 18:40 UTC FW27d ago 14 held half 13.8 days 1
Fri 18 Sep, 00:10 UTC41d ago 16 halved by day 8 13.8 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 should you expect from wipe day on Distorted - PVE 3X - Events and Raidable Bases - Biweekly?

At their busiest, its recent wipes drew 18 players on average. After the latest wipe, numbers topped out at 46 hours. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. When it didn't hold, by day 8 it fell below half.

When does Distorted - PVE 3X - Events and Raidable Bases - Biweekly wipe?

Its tag guides the prediction: too few of Distorted - PVE 3X - Events and Raidable Bases - Biweekly's wipes are on record to confirm its schedule. Thursday 29 October at 14:38 UTC is when its next wipe is due. 13 days 22 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.

Lists and filters

How should you read the tags on Distorted - PVE 3X - Events and Raidable Bases - Biweekly?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): Its browser listing: East Asia from Distorted - PVE 3X - Events and Raidable Bases - Biweekly. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Distorted - PVE 3X - Events and Raidable Bases - Biweekly appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Distorted - PVE 3X - Events and Raidable Bases - Biweekly: 3x Rust servers, checked live, Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 3x.

Player count

What position does Distorted - PVE 3X - Events and Raidable Bases - Biweekly hold among Rust servers?

Ranked by seven-day player hours, Distorted - PVE 3X - Events and Raidable Bases - Biweekly sits at #1,234 and #125 in Asia, inside the top 6%.

How full does Distorted - PVE 3X - Events and Raidable Bases - Biweekly get?

8 of 200 slots are filled on Distorted - PVE 3X - Events and Raidable Bases - Biweekly right now. Check: players over seven days. Average 6, peak 24. Check: 48-hour peak. 15:00 UTC, 13 players on average.

Server details

What location is Distorted - PVE 3X - Events and Raidable Bases - Biweekly hosted in?

Reading: location. The EA tag puts Distorted - PVE 3X - Events and Raidable Bases - Biweekly in Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 110.235.108.197:28015.

What Rust version is Distorted - PVE 3X - Events and Raidable Bases - Biweekly on?

Reading: Distorted - PVE 3X - Events and Raidable Bases - Biweekly, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for Distorted - PVE 3X - Events and Raidable Bases - Biweekly?

Over the last 48 hours the average was 207 server fps; the floor was 138. Reading: 159,026 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,979 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is Distorted - PVE 3X - Events and Raidable Bases - Biweekly, and is it online now?

Distorted - PVE 3X - Events and Raidable Bases - Biweekly reports online. Status: normal. Reading: uptime. About 4 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Distorted - PVE 3X - Events and Raidable Bases - Biweekly enforce, and what are its settings?

Gather rate check: 3x. That comes from the name Distorted - PVE 3X - Events and Raidable Bases - Biweekly. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: no combat against other players. 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 Distorted - PVE 3X - Events and Raidable Bases - Biweekly on?

Check: map. Procedural, size 4,250, seed 1289664801, generated by the game on Distorted - PVE 3X - Events and Raidable Bases - Biweekly. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto Distorted - PVE 3X - Events and Raidable Bases - Biweekly?

To join: start Rust, press F1 and type client.connect 110.235.108.197:28015. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/R4DsthDNr is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^b,EA,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp200
Max players The server holds 200 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EA
East Asia Its browser listing: East Asia.

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.