A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,323 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 6,385 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (A); population is 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
Every five minutes, from the Steam server list.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
EU · groups of 16+ · 2x · monthly · 300 on average
107 / 150
Quick answers
from the figures on this page
Server details
In what location does VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE sit?
The name of VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE points to Europe, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 179.254.167.22:28015.
How dependable is VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE, and is it online at the moment?
Right now, VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE is online. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 16 October 2026.
What Rust version is VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE on?
The server VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE is on Rust network protocol 2634 and build 167781 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE reset?
VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 12 days 6 hours.
Player count
Where does VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE sit among Rust servers?
Over the last seven days, VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE has #15,323 for player hours, in the top 69% of all ranked servers.
Is VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE a busy server?
With 40 slots available, VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
How should you read the tags on VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE?
You'll see VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE tagged with gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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 lists and filters on Rust Server Score show VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE?
Rust Server Score lists that include VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 2x.
Map and rules
What settings and rules apply on VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE?
The name of VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE points to a 2x gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE?
A procedural map, generated by the game, is what VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE runs.
Getting in
How should you connect to VANTA EU | 2X SOLO/DUO/TRIO | WEEKLY WIPE?
To connect, start Rust, press F1, and type client.connect 179.254.167.22:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max players40 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 uptime (A); population is the one to work on (F).