RUST METRICSFlight deck · live data
Data live Servers11,679 Players48,756 Populated3,222 Fresh wipes 3 h129 Scan5 min
‹ All servers103.91.211.6:20002
Offline Full Queue Fresh wipe Wipe due No query

qaqaesd2

Offline 103.91.211.6:20002 checked 34d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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,498top 68%
Last wipe34d 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, measured since 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Sep24 Sep25 Sep27 Sep28 Sep30 Sep

Top 68% 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 23 Sep, 03:20 UTC34d ago 0 – running 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.

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 timing

What happens on qaqaesd2 when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does qaqaesd2 follow?

Its rhythm cannot be told from the wipes of qaqaesd2 on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 34 days 21 hours ago.

Tag meanings

How should you read the tags on qaqaesd2?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from qaqaesd2. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does qaqaesd2 appear in Rust Metrics lists and filters?

On Rust Metrics, qaqaesd2 sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does qaqaesd2 sit in the rankings?

Player hours over seven days put qaqaesd2 at #15,498, in the top 68% of all ranked servers.

What is the population on qaqaesd2?

Reading for qaqaesd2: offline at this moment; last seen 34 days 16 hours ago.

Operator and location

Where does qaqaesd2 sit?

No region comes from qaqaesd2. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 103.91.211.6:20002.

What Rust version is qaqaesd2 on?

Rust network protocol 2633 and build 165217 on Linux is the build qaqaesd2 runs. Check: protocol. To join, your game must match; Steam handles the update.

Is qaqaesd2 up, and how often does it stay up?

qaqaesd2 reports offline. The last reading came 34 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 22 September 2026.

Map and rules

How is qaqaesd2 configured, and what rules are in force?

No gather rate appears in the name: qaqaesd2. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on qaqaesd2?

Size 3,000 and seed 17664: the game generates the procedural map on qaqaesd2 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join qaqaesd2?

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

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players 40 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.