Working its way up from the back of the class: #15,295 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
43/ 100
F
Slipped a little: down 2,057 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 70% of all ranked servers, and #626 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WWW·
W······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 19:11 UTC15d ago
1
–
running
0
Sat 10 Oct, 19:57 UTC17d ago
1
halved by day 1
2 days
0
Fri 9 Oct, 14:40 UTC18d ago
1
–
1.2 days
0
Thu 8 Oct, 13:20 UTC19d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by VEXA TEST. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 167.148.181.100:28015.
How reliable is VEXA TEST, and is it up?
The server is down: VEXA TEST is offline now, with the last sighting 10 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 5 October 2026, Rust Server Score saw it for the first time.
On what Rust version does VEXA TEST sit?
Rust network protocol 2634 and build 167781 on Linux is what VEXA TEST runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does VEXA TEST wipe its map?
No next wipe can be predicted for VEXA TEST, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 15 days 12 hours.
What happens on VEXA TEST when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
Where does VEXA TEST place in the wider field of Rust servers?
Over the last seven days, VEXA TEST has #15,295 for player hours, in the top 70% of all ranked servers. In the quad group, it ranks #626.
What does the population on VEXA TEST look like?
VEXA TEST is offline at the moment; the last time it was seen was 10 days 9 hours ago.
Lists and filters
How should you read the tags on VEXA TEST?
You'll see VEXA TEST tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts4 (Group limit): No team may go above 4; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature VEXA TEST?
These Rust Server Score lists count VEXA TEST among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Quad.
Map and rules
Which rules does VEXA TEST enforce, and what are its settings?
You will find no gather rate in the name of VEXA TEST. You can have up to 4 players in a group (quad). It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map VEXA TEST uses?
VEXA TEST runs a game-generated procedural map at size 1,000, seed 1. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Discord.gg/osmanlırust.
Getting in
What is the way to join VEXA TEST?
Enter client.connect 167.148.181.100:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts4,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts4
Group limitNo team may go above 4.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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.
A term to build on. Strongest in momentum (F); wipes are the one to work on (F).