RUST METRICSFlight deck · live data
Data live Servers11,617 Players35,735 Populated2,880 Fresh wipes 3 h74 Scan5 min
‹ All servers1.173.46.101:28015
Offline Full Queue Fresh wipe Wipe due No query

[TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]

Offline 1.173.46.101:28015 checked 9h ago

3x biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Wed 21:00 UTC
0 8 15 22 30 PAX 0 /30

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 31 SERVER FPS

Server fps

48 h low 31 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 96,570 ×1000

Entities

48 h range 96,570–125,573 · memory 2,559 MB
1239 ET SINCE RESTART 00:01

Uptime

0 h 1 min since its last restart, at the last reading
7-day average0peak 4
Rank#6,368top 29%
Last wipe13d agobiweekly schedule
Next wipe8hThu 29 Oct, 15:38 UTC
Memory2,559MB48 h peak 4 players
REC 1

Players

AveragePeak
0123407:0014:0022:0005:0013:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040007:0014:0022:0005:0013:0021:00

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

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

PLAN

Wipe schedule

Next wipe Thursday 29 October, 15:38 UTC, in 8h. Biweekly: 14 days after its last wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What wipe timing does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] follow?

The estimate for [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]'s next wipe comes from biweekly: 14 days after its last wipe. On Thursday 29 October at 15:38 UTC its next wipe is due. The world in play was created 13 days 15 hours ago. The tags carry an every-two-weeks wipe schedule.

Tags

How should you read the tags on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

Tags published by [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp30 (Max players): Slots: 30; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

These Rust Metrics lists carry [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]: 3x Rust servers, checked live, Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 3x.

Population

What position does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] hold among Rust servers?

Player hours over seven days put [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] at #6,368, in the top 29% of all ranked servers.

How full does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] get?

[TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is not responding; status offline, last seen 9 hours ago. Seven-day check: 0 players on average. Peak reading: 4. Check: 48-hour peak. 14:00 UTC, 4 players on average.

Server

What location is [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] hosted in?

Check: location. No region tag comes from [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ], but the name points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 1.173.46.101:28015.

What Rust version is [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] on?

Reading: [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ], Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is performance on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] within range?

Over the last 48 hours the average was 194 server fps; the floor was 31. Check: entities. The peak was 125,573, counting buildings, deployables and the rest of the world. Reading: 3,951 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ], and is it online?

Check: connection. [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is offline at this moment. Last contact was 9 hours ago. Reading: uptime. About 1 minutes ago it restarted, on its own count. Reading: 96% uptime over the last 3 full days. It was up 69 of 72 hours. Check: first contact. Rust Metrics logged it on 25 October 2026.

Rules and settings

What rules does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] enforce, and what are its settings?

The name carries the rate: 3x gather on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]. The group cap is 8 players, which is the default in the game. Mode check gives pve; no combat against other players. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] on?

Size 4,300 and seed 886786260: the game generates the procedural map on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How do you connect to [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

Check: join. Open Rust, press F1, then enter client.connect 1.173.46.101:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/74D93DqU.

PLACARDS

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp30
Max players Slots: 30.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.