Rust Server TrendsSeismic network · station log
Recording Stations11,790 Players66,598 Active3,624 Wipes · 3 h126 48 h

Station EA-14682 · recording

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours

Online EA 167.104.102.100:28015 checked 11m ago

2x trio weekly wipes vanillamoddedoxide
Connect
Players now
0/ 150
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#14,682
top 66% · #495 in EA
Last wipe
5d ago
weekly schedule
Next wipe
1d 11h
Fri 30 Oct, 09:25 UTC
Seismic record · station EA-14682 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 150 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123423:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608023:0008:0017:0001:0010:0020: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 20 Sep. 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 66% of all ranked servers, top 88% in EA, and #508 of the trio servers (top 81%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:25 UTC, in 1d 11h. Its weekly schedule tag · low confidence

usual gap
14.4 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
0%else halves by day 2.5

Coming wipes

  1. 1d 11hFri 30 Oct, 09:25 UTC
  2. 7d 20hThu 5 Nov, 19:00 UTCFW
  3. 8d 11hFri 6 Nov, 09:25 UTC
  4. 15d 11hFri 13 Nov, 09:25 UTC
  5. 22d 11hFri 20 Nov, 09:25 UTC
  6. 29d 11hFri 27 Nov, 09:25 UTC
  7. 35d 20hThu 3 Dec, 19:00 UTCFW
  8. 36d 11hFri 4 Dec, 09:25 UTC

The first 48 hours of its last wipes

Fri 23 OctFri 2 OctThu 24 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 09:25 UTC5d ago M0.0rising 1 – running 0
Fri 2 Oct, 19:26 UTC26d ago M0.0rising 1 halved by day 2 20.6 days 0
Thu 24 Sep, 14:15 UTC34d ago M0.3rising 2 halved by day 3 8.2 days 0

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
Zev | Зэвэрсэн Тал | Mongolia 2x Modded | Weekly EA · trio · 2x · weekly · 2 on average
1/ 50
QS『可乐』10.28/5倍/养老/三人/萌新礼包 EA · trio · weekly · 22 on average
27/ 100
WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPED EA · trio · 3x · weekly · 3 on average
0/ 100
[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/28 EA · trio · weekly · 132 on average
55/ 250
小海螺10.28号|14点新档|三人游玩 EA · trio · weekly · 28 on average
52/ 300
『元宇宙』10.27号新开/独狼/三人/萌新服 EA · trio · weekly · 27 on average
0/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

The procedural map on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is size 3,500 with seed 272704469, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Its name points to a gather rate of 2x on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. 3 players is the most a group can hold (trio). survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours right now?

A reading taken now shows 0 players on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, which has 150 slots. The seven-day average is 0 players, with a peak of 1.

How does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours rank against other Rust servers?

For player hours across the last seven days, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours takes #14,682 overall and #495 in Asia, inside the top 66% of all ranked servers. It sits at #508 among trio servers.

Operator and location

How reliably does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours stay online?

As recorded now, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is running. Its reported uptime points to a restart about 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. On 20 September 2026 it was recorded for the first time by Rust Server Trends.

Does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hold a steady tick rate?

Its average server fps over the last 48 hours was 49, and it never dropped below 36. The world held up to 66,967 entities at its peak, buildings and deployables included. It reached a ceiling of 2,335 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hosted?

With its EA tag, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 167.104.102.100:28015.

What build of Rust does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours use?

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

The recent wipes averaged a busiest count of 1 players. 5 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 2.5.

On what timetable does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours run its wipes?

The prediction is taken from its tag, since [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours has too few wipes on record to confirm the schedule. The date of its next wipe is Friday 30 October at 09:25 UTC. The present world dates from 5 days 12 hours. Its tags state a weekly wipe schedule.

Tags

What do the server tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours mean?

These are the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp150 (Max players): 150 slots are available; ts3 (Group limit): Teams are capped at 3 players; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^w (Weekly): A wipe comes once a week; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): In the server browser it appears under East Asia. 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 [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear?

These Rust Server Trends lists include [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: 2x Rust servers, listed live, Modded Rust servers, tracked live and Best trio Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.

Join the server

How do you connect to [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Enter client.connect 167.104.102.100:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://discord.com/invite/6DAQjtGZD6.

Instrument codes

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts3,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp150
Max players 150 slots are available.
ts3
Group limit Teams are capped at 3 players.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^w
Weekly A wipe comes once a week.

Difficulty

^v
Vanilla Unchanged from Facepunch's release: no altered rates, kits or rules.

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.

Region

EA
East Asia In the server browser it appears under East Asia.

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.