Rust Data

rustdata.spaceservers167.148.181.100:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 167.148.181.100:28015 checked 9d ago

VEXA TEST

quad oxide

Connect

srv = rust.server("167.148.181.100:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak –
rank #15,295 # top 70%
last wipe 15d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 5 Oct. 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
15k10k15k20k5 Oct9 Oct13 Oct16 Oct20 Oct24 Oct

Top 70% of all ranked servers, and #626 of the quad servers (top 76%). Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

usual gap1.2 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 12 OctSat 10 OctFri 9 Oct
01234+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 Mon 12 Oct, 19:11 UTC15d ago 1 NaN running 0
1 Sat 10 Oct, 19:57 UTC17d ago 1 halved by day 1 2 days 0
2 Fri 9 Oct, 14:40 UTC18d ago 1 NaN 1.2 days 0
3 Thu 8 Oct, 13:20 UTC19d ago 1 NaN 1.1 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.

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

Map

1000 · seed 1
Map of VEXA TEST
map
Discord.gg/osmanlırust
size
1000
seed
1

Server

srv.info()
address
167.148.181.100:28015
region
–
max players
40
group limit
quad
wipe schedule
–
last wipe
12 Oct 2026, 19:11 UTC
hostname
–
first seen
5 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] TideRust - Solo/Duo/Trio/Quad | Monthly |No BP WipesEU · quad · monthly · 108 on average196/250
1[TR/EU] VATAN | Solo/Duo/Trio/Quad | Yeni başlayanlar içinEU · quad · monthly · 79 on average336/375
2WARBANDITS.GG |Solo/Duo/Trio/Quad|Weekly| JUST WIPEDNA · quad · weekly · 49 on average77/200
3Cali.gg | No KOS | Noob Friendly | Active AdminsNA · quad · biweekly · 36 on average15/100
4[EU] Bold | Solo/Duo/Trio/Quad | Newbie/Noob Friendly | BiweeklEU · quad · biweekly · 30 on average29/150
5『小宇宙』10.27号/新开/四人服/萌新服EA · quad · weekly · 21 on average0/200

Quick answers

From the figures on this page.

Population data

How does VEXA TEST compare in the rankings?

Rank #15,295 on seven-day player hours for VEXA TEST, within the top 70% of all ranked servers. Its position in the quad group is #626.

How many players does VEXA TEST hold at once?

Offline now for VEXA TEST, with the last sample 9 days 23 hours ago.

Server data

Which Rust version is VEXA TEST on?

Version Rust network protocol 2634 and build 167781 on Linux is reported by VEXA TEST. Joining needs the same protocol on your game; Steam handles the update.

Is VEXA TEST up, and what does its uptime show?

VEXA TEST is offline at this refresh; the last response came 9 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 5 October 2026.

In which location is VEXA TEST hosted?

No region is published by VEXA TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 167.148.181.100:28015.

Settings and map

What rules and settings are recorded for VEXA TEST?

No gather rate appears in the name: VEXA TEST. Up to 4 players may share a group (quad). Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has VEXA TEST selected?

The game generates the map on VEXA TEST: procedural, size 1,000, seed 1. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Discord.gg/osmanlırust.

Wipes and dates

On what schedule does VEXA TEST wipe?

VEXA TEST wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 15 days 1 hours ago, and that is the one in play.

What is wipe day on VEXA TEST like?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Tags, lists

Where does VEXA TEST appear among Rust Data lists and filters?

These Rust Data lists include VEXA TEST: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Quad.

Which meanings do the tags on VEXA TEST hold?

The game's server browser reads these tags from VEXA TEST: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): The server lists 40 slots; ts4 (Group limit): Team size tops out at 4; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod). Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join VEXA TEST?

In Rust, F1 opens the console: type client.connect 167.148.181.100:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$r?,v2634,gmrust,cs167781,ts4,^o

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players The server lists 40 slots.
ts4
Group limit Team size tops out at 4.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is 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 80,134 players 11,840 servers online