Rust Server TrendsSeismic network · station log
Recording Stations11,805 Players79,944 Active3,786 Wipes · 3 h105 48 h

Station XX-6358 · recording

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

Online 1.173.46.101:28015 checked 11m ago

3x biweekly wipes moddedoxidepve
Connect
Players now
0/ 30
0% full
Motion · 24 h
M0.0falling
−1 players on the day
7-day average
0
peak 4
Rank
#6,358
top 29%
Last wipe
13d ago
biweekly schedule
Next wipe
19h
Thu 29 Oct, 15:38 UTC
Seismic record · station XX-6358 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 30 slots
Motion · 24 h
M0.0falling−1 players
Sharpest hour
+2into Tue 14:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123421:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040021:0006:0015:0000:0009:0019: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.

Channel 3 · rank movement

Rank

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

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Distorted - PVE 3X - Events and Raidable Bases - Biweekly EA · groups of 8+ · 3x · biweekly · 7 on average
0/ 200
RnC PVE 3X | Wiped: 15/10 EA · groups of 30+ · 3x · biweekly · 2 on average
0/ 50
PapC PVE Server x3 Philippines EA · groups of 8+ · 3x · biweekly · 1 on average
0/ 50
[KR] 쿠키서버 PVE/X3/NPC레이드/낚시/초보 EA · groups of 8+ · 3x · monthly · 15 on average
7/ 100
[VN/SEA] VietRust x2 | PvEvP Chill - Farmer Friendly EA · groups of 8+ · 2x · biweekly · 2 on average
0/ 40
모코코서버 [PVE|X3|이벤트|초보] EA · groups of 8+ · 3x · monthly · 2 on average
0/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

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

The procedural map on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is size 4,300 with seed 886786260, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

Going by its name, [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] runs 3x gather. The group limit is 8 players, the game's default. In pve mode, no player-versus-player fighting. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

At this moment, [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] records 0 players across 30 slots. Across seven days this server recorded an average of 0 players and a peak of 4. Averaged over the last 48 hours, the busiest hour was 14:00 UTC at 4 players.

How does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] rank against other Rust servers?

Over the last seven days, [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] recorded enough player hours to reach #6,358 worldwide, placing it in the top 29% of all ranked servers.

Server facts

How reliably does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] stay online?

As recorded now, [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is running. Its reported uptime points to a restart about 7 hours ago. Of the 48 hours in the last 2 full days, it was up for 48, or 100% of the time. On 25 October 2026 it was recorded for the first time by Rust Server Trends.

How well does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] perform under load?

Across the last 48 hours it averaged 205 server fps, with a floor of 102. Buildings, deployables and all the rest of the world's entities brought it to a high of 125,573. It reached a ceiling of 3,951 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] hosted?

The name of [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] points to Asia, even though it publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 1.173.46.101:28015.

Which Rust version is [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] running?

[TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

On what timetable does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] run its wipes?

From biweekly: 14 days after its last wipe the next wipe of [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is estimated. Thursday 29 October at 15:38 UTC is when its next wipe is due. The present world dates from 13 days 4 hours. Every two weeks it wipes, according to the schedule in its tags.

Lists and tags

What do the server tags on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] mean?

These are the tags [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp30 (Max players): Slots: 30; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] appear?

You will find [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] on the following Rust Server Trends lists: 3x Rust servers, by live population, Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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.

Connecting

What steps get you onto [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]?

Enter client.connect 1.173.46.101:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/74D93DqU.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp30
Max players Slots: 30.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Gameplay

^p
PvE The danger comes from the world, not from other players.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.