Rust Data

rustdata.spaceservers172.240.15.67:25568.ipynb

Run all rust-data · live

‹ All servers

Online 172.240.15.67:25615 checked 10m ago

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

oxide

Connect

srv = rust.server("172.240.15.67:25568")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 2
rank #5,823 # top 26%
last wipe 6d ago # no schedule published
next wipe 22h # Fri 30 Oct, 03:49 UTC

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5206:0015:0000:0008:0017:0003:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · fixed weekdays

srv.wipe_schedule()

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

inatkind
022hFri 30 Oct, 03:49 UTCwipe
17d 13hThu 5 Nov, 19:00 UTCFW force wipe
27d 22hFri 6 Nov, 03:49 UTCwipe
314d 22hFri 13 Nov, 03:49 UTCwipe
421d 22hFri 20 Nov, 03:49 UTCwipe
528d 22hFri 27 Nov, 03:49 UTCwipe
635d 13hThu 3 Dec, 19:00 UTCFW force wipe
735d 22hFri 4 Dec, 03:49 UTCwipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 03:49 UTC6d ago 1 NaN running 0
1 Fri 9 Oct, 03:01 UTC20d ago 2 halved by day 11 14 days 1
2 Fri 2 Oct, 03:42 UTC27d ago 2 held half 7 days 0
3 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.

display(srv.map, srv.info())

Map

6000 · seed 4636
Map of 10/22 Vengeance | Solo/Duo/Trio | NoDecay
map
Procedural Map
size
6000
seed
4636
Open on RustMaps

Server

srv.info()
address
172.240.15.67:25615
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
23 Oct 2026, 03:49 UTC
hostname
–
first seen
18 Sep 2026

About this server · in its own words

print(srv.description)
Welcome to Vengeace! -No Decay -Group Limit:3 -Map Size:6000 -Current Wipe: 10/22 -Next Wipe: ForceWipe

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 542 on average145/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average131/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average19/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average46/200

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does 10/22 Vengeance | Solo/Duo/Trio | NoDecay rank?

Player hours over seven days put 10/22 Vengeance | Solo/Duo/Trio | NoDecay at #5,823, in the top 26% of the ranked set.

What population does 10/22 Vengeance | Solo/Duo/Trio | NoDecay carry?

10/22 Vengeance | Solo/Duo/Trio | NoDecay reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 01:00 UTC, averaging 2 players.

Server facts

What does performance look like on 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

The 48-hour average is 111 server fps, with a low of 78. Entity numbers reached 200,879, and that includes buildings, deployables and the rest. Memory peaked at 5,394 MB. What players call lag is these two fields together: low fps and a rising entity count.

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

Rust network protocol 2635 and build 168909 on Linux is what 10/22 Vengeance | Solo/Duo/Trio | NoDecay runs. Steam updates your game for you, but the protocol must match to join.

Is 10/22 Vengeance | Solo/Duo/Trio | NoDecay up, and what does its uptime show?

10/22 Vengeance | Solo/Duo/Trio | NoDecay reports itself online at the current refresh. Count back 4 days 2 hours from its reported uptime to get the last restart. Uptime of 96% across the last 7 full days: 161 hours of 168. The first row Rust Data holds for it is dated 18 September 2026.

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

There is no region published for 10/22 Vengeance | Solo/Duo/Trio | NoDecay. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 172.240.15.67:25615.

Settings and map

Which rules apply on 10/22 Vengeance | Solo/Duo/Trio | NoDecay, and what settings?

The name 10/22 Vengeance | Solo/Duo/Trio | NoDecay carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has 10/22 Vengeance | Solo/Duo/Trio | NoDecay selected?

The game generates the map on 10/22 Vengeance | Solo/Duo/Trio | NoDecay: procedural, size 6,000, seed 4636. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does 10/22 Vengeance | Solo/Duo/Trio | NoDecay wipe, and how often?

The wipe rhythm for 10/22 Vengeance | Solo/Duo/Trio | NoDecay is every Friday at 03:49 UTC. The schedule puts the next wipe on Friday 30 October at 03:49 UTC. The world it runs now was generated 6 days 1 hours ago.

On 10/22 Vengeance | Solo/Duo/Trio | NoDecay, what happens on wipe day?

The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 33% of recent wipes. Otherwise the crowd fell below half by day 8.5.

Tags, lists

Which Rust Data filters and lists contain 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

These Rust Data lists include 10/22 Vengeance | Solo/Duo/Trio | NoDecay: Rust community servers, unfiltered. It appears under these filters on the server list: 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.

Which meanings do the tags on 10/22 Vengeance | Solo/Duo/Trio | NoDecay hold?

The game's server browser reads these tags from 10/22 Vengeance | Solo/Duo/Trio | NoDecay: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into 10/22 Vengeance | Solo/Duo/Trio | NoDecay?

The manual route: launch Rust, F1, then client.connect 172.240.15.67:25615. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (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.

Rust Data 31,131 players 11,626 servers online