RUST METRICSFlight deck · live data
Data live Servers11,626 Players31,131 Populated2,740 Fresh wipes 3 h70 Scan5 min
‹ All servers172.240.15.67:25615
Online Full Queue Fresh wipe Wipe due No query

10/22 Vengeance | Solo/Duo/Trio | NoDecay

Online 172.240.15.67:25615 checked 11m ago

oxide
COM 1 · connect
Launch Rust and join

Server instruments

last reading Thu 03: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 94 SERVER FPS

Server fps

48 h low 78 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 200,380 ×1000

Entities

48 h range 198,102–200,879 · memory 4,601 MB
1239 ET SINCE RESTART 4D 02H

Uptime

4 days 2 hours since its last restart, at the last reading
7-day average0peak 2
Rank#5,823top 26%
Last wipe6d agono schedule published
Next wipe22hFri 30 Oct, 03:49 UTC
Memory4,601MB48 h peak 2 players
REC 1

Players
AveragePeak
00.511.5206:0015:0000:0008:0017:0003:00

Hourly average and peak, UTC.

REC 2

Server performance
05010015020006:0015:0000:0008:0017:0003: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 18 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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 03:49 UTC, in 22h. Every Friday at 03:49 UTC · medium confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held33%else halves by day 8.5

Coming wipes

  1. WPT 1Fri 30 Oct, 03:49 UTC22h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 13hFW
  3. WPT 3Fri 6 Nov, 03:49 UTC7d 22h
  4. WPT 4Fri 13 Nov, 03:49 UTC14d 22h
  5. WPT 5Fri 20 Nov, 03:49 UTC21d 22h
  6. WPT 6Fri 27 Nov, 03:49 UTC28d 22h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 13hFW
  8. WPT 8Fri 4 Dec, 03:49 UTC35d 22h

The first 48 hours of its last wipes

Fri 23 OctFri 9 OctFri 2 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 03:49 UTC6d ago 1 – running 0
Fri 9 Oct, 03:01 UTC20d ago 2 halved by day 11 14 days 1
Fri 2 Oct, 03:42 UTC27d ago 2 held half 7 days 0
Fri 25 Sep, 02:35 UTC34d ago 2 halved by day 6 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

Wipe schedule

What happens on 10/22 Vengeance | Solo/Duo/Trio | NoDecay when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. It fell below half by day 8.5 when it didn't.

What wipe timing does 10/22 Vengeance | Solo/Duo/Trio | NoDecay follow?

The wipe rhythm of 10/22 Vengeance | Solo/Duo/Trio | NoDecay is every Friday at 03:49 UTC. Friday 30 October at 03:49 UTC is when its next wipe is due. The world it runs now was made 6 days 1 hours ago.

Tags

Which tags does 10/22 Vengeance | Solo/Duo/Trio | NoDecay carry, and what do they mean?

Tags published by 10/22 Vengeance | Solo/Duo/Trio | NoDecay, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does 10/22 Vengeance | Solo/Duo/Trio | NoDecay appear in Rust Metrics lists and filters?

Rust Metrics lists featuring 10/22 Vengeance | Solo/Duo/Trio | NoDecay: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does 10/22 Vengeance | Solo/Duo/Trio | NoDecay sit in the rankings?

Ranking for 10/22 Vengeance | Solo/Duo/Trio | NoDecay: #5,823 on seven-day player hours, top 26% of all ranked servers.

What is the population on 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

Current headcount on 10/22 Vengeance | Solo/Duo/Trio | NoDecay: 0 players, 50 slots available. Check: players over seven days. Average 0, peak 2. The last 48 hours peaked at 01:00 UTC, averaging 2 players at that hour.

Server

Which location does 10/22 Vengeance | Solo/Duo/Trio | NoDecay run from?

Reading: location. 10/22 Vengeance | Solo/Duo/Trio | NoDecay gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 172.240.15.67:25615.

What Rust version is 10/22 Vengeance | Solo/Duo/Trio | NoDecay on?

Rust network protocol 2635 and build 168909 on Linux is the build 10/22 Vengeance | Solo/Duo/Trio | NoDecay runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

Over the last 48 hours the average was 111 server fps; the floor was 78. Check: entities. The peak was 200,879, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 5,394 MB. What players call lag comes from low fps and an entity count on the rise.

Is 10/22 Vengeance | Solo/Duo/Trio | NoDecay up, and how often does it stay up?

Reading: online. 10/22 Vengeance | Solo/Duo/Trio | NoDecay answers right now. Reading: uptime. About 4 days 2 hours ago it restarted, on its own count. Uptime for the last 7 full days: 161 of 168 hours, or 96%. The first sighting on Rust Metrics was 18 September 2026.

Rules and settings

What rules does 10/22 Vengeance | Solo/Duo/Trio | NoDecay enforce, and what are its settings?

No gather rate appears in the name: 10/22 Vengeance | Solo/Duo/Trio | NoDecay. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is 10/22 Vengeance | Solo/Duo/Trio | NoDecay on?

Size 6,000 and seed 4636: the game generates the procedural map on 10/22 Vengeance | Solo/Duo/Trio | NoDecay from them. 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 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

To join: start Rust, press F1 and type client.connect 172.240.15.67:25615. 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,cs168909,ts8,^o

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

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.