Rust Server TrendsSeismic network · station log
Recording Stations11,699 Players65,959 Active3,548 Wipes · 3 h117 48 h

Station XX-15315 · no signal

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

Offline 1.173.19.49:28015 checked 8d ago

3x biweekly wipes moddedoxidepve
Connect
Players now
0/ 30
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,315
top 69%
Last wipe
12d ago
biweekly schedule
Next wipe
1d 3h
Thu 29 Oct, 15:38 UTC
Seismic record · station XX-15315 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 30 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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 15 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
15k10k15k20k15 Oct17 Oct19 Oct22 Oct24 Oct26 Oct

Top 69% 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 1d 3h. 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
13/ 200
RnC PVE 3X | Wiped: 15/10 EA · groups of 30+ · 3x · biweekly · 2 on average
2/ 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
25/ 100
[VN/SEA] VietRust x2 | PvEvP Chill - Farmer Friendly EA · groups of 8+ · 2x · biweekly · 2 on average
3/ 40
모코코서버 [PVE|X3|이벤트|초보] EA · groups of 8+ · 3x · monthly · 2 on average
3/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

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

Generated by the game, the map on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is procedural, size 4,300 with seed 886786260. Size and seed produce the same map, so RustMaps can show it from this page.

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 combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] right now?

[TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is not responding at this moment and is offline, last seen 8 days 16 hours ago.

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 #15,315 worldwide, placing it in the top 69% of all ranked servers.

Operator and location

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

As recorded now, [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is not reachable, the last contact having been 8 days 16 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 15 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] run from?

Its name points to Asia, but [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 1.173.19.49:28015 is the address it uses.

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

[TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] is running Rust network protocol 2634 and build 167781 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

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

An estimate from biweekly: 14 days after its last wipe gives [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ]'s next wipe. The date of its next wipe is Thursday 29 October at 15:38 UTC. The present world dates from 12 days 20 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): 30 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^b (Biweekly): A wipe comes every second week; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

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

The Rust Server Trends lists that take in [TW] AixWalker [ PVE | 3X | Raidable Bases | Events ] are: 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.

How to join

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

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

Instrument codes

Server tags

what each one means

Published as mp30,ptrak,$r?,v2634,^b,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp30
Max players 30 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build Game build: 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Gameplay

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

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running 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.