StatusLive Servers online11,798 Players68,197 Populated3,637 Wiped · 3 h131 Interval5 min Date28 OCT 2026

DWG RG-S15295Server sheetchecked 11d ago

VEXA TEST

Offline 167.148.181.100:28015 checked 11d ago

quad oxide
Connect
Players now 0/ 40 0% full
7-day average0peak –
Rank#15,295top 70%
Last wipe16d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on VEXA TEST
Fig. 2

Server performance

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 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.

Fig. 3Rank on player hours, daily
Schedule

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 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 19:11 UTC16d ago 1 – running 0
Sat 10 Oct, 19:57 UTC18d ago 1 halved by day 1 2 days 0
Fri 9 Oct, 14:40 UTC19d ago 1 – 1.2 days 0
Thu 8 Oct, 13:20 UTC20d ago 1 – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[EU] TideRust - Solo/Duo/Trio/Quad | Monthly |No BP WipesEU · quad · monthly · 123 on average
130 / 250
02 264 / 350
03
WARBANDITS.GG |Solo/Duo/Trio/Quad|Weekly| JUST WIPEDNA · quad · weekly · 54 on average
33 / 200
04 0 / 165
05
Cali.gg | No KOS | Noob Friendly | Active AdminsNA · quad · biweekly · 32 on average
7 / 100
06
[LATAM] VAINILLA Solo/Duo/Trio/Quad | 28/10 WipeSA · quad · weekly · 30 on average
313 / 350
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for VEXA TEST, and is it up?

Last seen 11 days ago; right now VEXA TEST is offline. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 5 October 2026.

In which location is VEXA TEST hosted?

A region is not published by VEXA TEST. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 167.148.181.100:28015 is its address.

What Rust version is recorded for VEXA TEST?

Rust network protocol 2634 and build 167781 on Linux: that is what VEXA TEST runs. Steam updates your game, which must be on the same protocol for you to join.

Counts

What player count is recorded on VEXA TEST?

No response from VEXA TEST; the server was last seen 11 days ago.

In the rankings, which position does VEXA TEST hold?

Player hours over seven days place VEXA TEST at #15,295, within the top 70% of ranked servers. #626 against other quad servers.

Wipe times

What is recorded on VEXA TEST on wipe day?

The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. By day 1 the crowd had fallen below half on the wipes where it did not hold.

On VEXA TEST, when do wipes occur?

No next wipe can be predicted for VEXA TEST: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 16 days 2 hours ago.

Rules and settings

Which rules and settings are recorded for VEXA TEST?

No gather rate is stated in the name of VEXA TEST. 4 players per group at most (quad). survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Community is its tab in the server browser. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

Which map has VEXA TEST loaded?

Size 1,000 with seed 1: that is the procedural map VEXA TEST runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. Recorded map name: Discord.gg/osmanlırust.

Filters

On Rust Graphs, which lists and filters contain VEXA TEST?

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

Which meaning is attached to each tag on VEXA TEST?

Tags published by VEXA TEST, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): Slots: 40; ts4 (Group limit): Teams hold no more than 4; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod). Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

How to join

By what method do you join VEXA TEST?

In Rust, press F1 and type client.connect 167.148.181.100:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp40
Max players Slots: 40.
ts4
Group limit Teams hold no more than 4.
v2634
Protocol Join only if your game is on protocol 2634.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

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.

KeyTag string decoded