RUST METRICSFlight deck · live data
Data live Servers11,596 Players34,270 Populated2,854 Fresh wipes 3 h64 Scan5 min
‹ All servers84.32.186.152:28015
Offline Full Queue Fresh wipe Wipe due No query

AloeSerVAC

Offline 84.32.186.152:28015 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,316top 70%
Last wipe10d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep7 Oct10 Oct19 Oct22 Oct25 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap12.8 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sun 18 OctMon 5 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 10:56 UTC9d ago 0 – running 0
Mon 5 Oct, 15:45 UTC22d ago 0 – 12.8 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on AloeSerVAC?

An average of 0 players came at the busiest on its recent wipes. 1 hours after the wipe, the crowd peaked on the latest wipe.

When does AloeSerVAC wipe?

The rhythm of AloeSerVAC's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 10 days ago.

Tags

How should you read the tags on AloeSerVAC?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from AloeSerVAC. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does AloeSerVAC appear in Rust Metrics lists and filters?

Rust Metrics lists featuring AloeSerVAC: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does AloeSerVAC hold among Rust servers?

Player hours over seven days put AloeSerVAC at #15,316, in the top 70% of all ranked servers.

How full does AloeSerVAC get?

AloeSerVAC is not responding; status offline, last seen 9 days 17 hours ago.

Operator and location

What location is AloeSerVAC hosted in?

No region tag on AloeSerVAC. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 84.32.186.152:28015.

What Rust version is AloeSerVAC on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by AloeSerVAC. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is AloeSerVAC, and is it online now?

AloeSerVAC reports offline. The last reading came 9 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on AloeSerVAC?

No gather rate appears in the name: AloeSerVAC. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is AloeSerVAC on?

Check: map. Procedural, generated by the game, on AloeSerVAC.

How to join

How can you get onto AloeSerVAC?

Check: join. Open Rust, press F1, then enter client.connect 84.32.186.152:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.