RUST METRICSFlight deck · live data
Data live Servers11,660 Players41,774 Populated2,991 Fresh wipes 3 h88 Scan5 min
‹ All servers109.248.4.20:35000
Offline Full Queue Fresh wipe Wipe due No query

InvokeRust WEX [X2, Vanilla, No Limit]

Offline 109.248.4.20:35000 checked 1d ago

2x moddedoxide
COM 1 · connect

Server instruments

last reading Mon 21:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

48 h low 103 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 66,720 ×1000

Entities

48 h range 66,416–68,647 · memory 2,532 MB
1239 ET SINCE RESTART 3D 00H

Uptime

3 days 0 hours since its last restart, at the last reading
7-day average0peak 3
Rank#5,503top 25%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Memory2,532MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75103:0007:0010:0014:0017:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020003:0007:0010:0014:0017:0021: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 19 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap5.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held25%else halves by day 2

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctMon 12 Oct
02468+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
Fri 23 Oct, 19:20 UTC4d ago 3 – running 1
Fri 16 Oct, 19:38 UTC11d ago 5 halved by day 2 7 days 4
Mon 12 Oct, 18:31 UTC15d ago 3 halved by day 2 4 days 0
Fri 9 Oct, 20:44 UTC18d ago 3 held half 2.9 days 0
Fri 2 Oct, 10:58 UTC25d ago 0 – 7.4 days 0
Fri 25 Sep, 12:10 UTC32d ago 1 halved by day 4 6.9 days 0
Mon 21 Sep, 14:30 UTC36d ago 4 halved by day 2 3.9 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 InvokeRust WEX [X2, Vanilla, No Limit] when wipe day comes?

At their busiest, its recent wipes drew 4 players on average. Peak crowd on the latest wipe: 0 hours in. Above half that peak the crowd stayed until the next wipe in 25% of recent wipes. It fell below half by day 2 when it didn't.

What wipe timing does InvokeRust WEX [X2, Vanilla, No Limit] follow?

There is no next wipe to predict: InvokeRust WEX [X2, Vanilla, No Limit] wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 4 days 7 hours ago the current world was made.

Tag meanings

Which tags does InvokeRust WEX [X2, Vanilla, No Limit] carry, and what do they mean?

Tags published by InvokeRust WEX [X2, Vanilla, No Limit], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show InvokeRust WEX [X2, Vanilla, No Limit]?

On Rust Metrics, InvokeRust WEX [X2, Vanilla, No Limit] sits in these lists: 2x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.

Player count

Where does InvokeRust WEX [X2, Vanilla, No Limit] sit in the rankings?

Player hours over seven days put InvokeRust WEX [X2, Vanilla, No Limit] at #5,503, in the top 25% of all ranked servers.

How full does InvokeRust WEX [X2, Vanilla, No Limit] get?

Status for InvokeRust WEX [X2, Vanilla, No Limit]: offline. Last seen 29 hours ago. Seven-day check: 0 players on average. Peak reading: 3. The last 48 hours peaked at 11:00 UTC, averaging 1 players at that hour.

Server details

Where does InvokeRust WEX [X2, Vanilla, No Limit] sit?

No region tag on InvokeRust WEX [X2, Vanilla, No Limit]. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 109.248.4.20:35000.

What Rust version is InvokeRust WEX [X2, Vanilla, No Limit] on?

Reading: InvokeRust WEX [X2, Vanilla, No Limit], Rust network protocol 2635 and build 167398, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is performance on InvokeRust WEX [X2, Vanilla, No Limit] within range?

Over the last 48 hours the average was 163 server fps; the floor was 103. Peak entity count: 68,647. Buildings, deployables and all else included. Check: memory. Peak use was 2,913 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is InvokeRust WEX [X2, Vanilla, No Limit], and is it online now?

InvokeRust WEX [X2, Vanilla, No Limit] reports offline. The last reading came 29 hours ago. Check: restart. The uptime it reports puts the last restart about 3 days ago. Uptime for the last 7 full days: 142 of 168 hours, or 85%. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Settings and map

What rules does InvokeRust WEX [X2, Vanilla, No Limit] enforce, and what are its settings?

The name carries the rate: 2x gather on InvokeRust WEX [X2, Vanilla, No Limit]. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is InvokeRust WEX [X2, Vanilla, No Limit] on?

Size 3,500 and seed 1622660352: the game generates the procedural map on InvokeRust WEX [X2, Vanilla, No Limit] from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join InvokeRust WEX [X2, Vanilla, No Limit]?

To join: start Rust, press F1 and type client.connect 109.248.4.20:35000. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

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

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.