StatusLive Servers online11,886 Players93,191 Populated4,074 Wiped · 3 h167 Interval5 min Date27 OCT 2026

DWG RG-S14680Server sheetchecked 11m ago

[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
7-day average0peak 1
Rank#14,680top 66% · #495 in EA
Last wipe4d agoweekly schedule
Next wipe2d 13hFri 30 Oct, 09:25 UTC
Fig. 1

Players

AveragePeak
0123420:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Fig. 1Players on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours
Fig. 2

Server performance

025507510020:0005:0014:0000:0009:0018: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

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

usual gap14.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5

Coming wipes

  1. 2d 13hFri 30 Oct, 09:25 UTC
  2. 8d 23hThu 5 Nov, 19:00 UTCFW
  3. 9d 13hFri 6 Nov, 09:25 UTC
  4. 16d 13hFri 13 Nov, 09:25 UTC
  5. 23d 13hFri 20 Nov, 09:25 UTC
  6. 30d 13hFri 27 Nov, 09:25 UTC
  7. 36d 23hThu 3 Dec, 19:00 UTCFW
  8. 37d 13hFri 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 09:25 UTC4d ago 1 – running 0
Fri 2 Oct, 19:26 UTC25d ago 1 halved by day 2 20.6 days 0
Thu 24 Sep, 14:15 UTC33d ago 2 halved by day 3 8.2 days 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Zev | Зэвэрсэн Тал | Mongolia 2x Modded | WeeklyEA · trio · 2x · weekly · 2 on average
2 / 50
02
QS『可乐』10.27/5倍/养老/三人/萌新礼包EA · trio · weekly · 21 on average
23 / 100
03
WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPEDEA · trio · 3x · weekly · 3 on average
1 / 100
04 2 / 180
05
『元宇宙』10.27号新开/独狼/三人/萌新服EA · trio · weekly · 31 on average
4 / 200
06 0 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours online, and what uptime has been recorded?

At this moment [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. About 21 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 20 September 2026.

Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours stable in the figures recorded?

Average server fps over the last 48 hours is 46; the lowest was 12. Counted at its highest: 66,918 entities, buildings, deployables and the rest of the world included. 2,314 MB is the memory peak. Players feel low fps and a climbing entity count as lag.

What location is recorded for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

In Asia [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself, tagged EA. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 167.104.102.100:28015.

What Rust version is recorded for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Rust network protocol 2635 and build 168909 on Linux: that is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs. To join, your game must be on the same protocol; Steam handles the update.

Counts

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

Current player count on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: 0, of 150 slots. Averaged across seven days, the player count is 0, with a peak of 1.

Against other Rust servers, where is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours placed?

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours also measures #495 in Asia on the same seven-day player-hour count, at #14,680 globally and in the top 66% of ranked servers. #505 against other trio servers.

Wipe data

What is recorded on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on wipe day?

An average of 1 players was recorded at the busiest point of its recent wipes. 5 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 2.5 the crowd had fallen below half on the wipes where it did not hold.

On [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, when do wipes occur?

Too few of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. On Friday 30 October at 09:25 UTC its next wipe is due. The world it runs now was made 4 days 10 hours ago. Its tags give a wipe schedule of one wipe a week.

Rules and settings

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

The name records 2x gather for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. A group tops out at 3 players (trio). survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Vanilla is the label it uses: rates, kits and rules are unchanged from Facepunch's release. VAC is on: that is Valve's anti-cheat.

On which map is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours played?

Size 3,500 with seed 272704469: that is the procedural map [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear among the Rust Graphs lists and filters?

These Rust Graphs lists include [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: Servers with a 2x gather rate, Modded Rust servers and Trio Rust servers, plotted live. On the server list, these filters bring it up: 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.

Which meaning is attached to each tag on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

gmrust (Game mode): Survival in standard Rust style; mp150 (Max players): 150 player slots; ts3 (Group limit): The team limit is 3; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^w (Weekly): A wipe occurs every week; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; EA (East Asia): The server browser lists it under East Asia are the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

What is the way to connect to [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Enter client.connect 167.104.102.100:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/6DAQjtGZD6.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp150
Max players 150 player slots.
ts3
Group limit The team limit is 3.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Wipe schedule

^w
Weekly A wipe occurs every week.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Region

EA
East Asia The server browser lists it 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.

KeyTag string decoded