Skip to the page
RUST ANALYTICS
LIVE54,828PLY11,646SRV
QUOTE 167.104.102.100:28015 Online EA checked 10m ago

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

2x trio weekly wipes vanillamoddedoxide
Players · last
0/ 150
+024h
0% full
Day range 0 1
7-day avg 0 peak 1
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 150
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak 1
Rank
#15,485
top 69% · #488 in EA
Rank · 7d ago
#12,288
3197 places down
Last wipe
11d ago
weekly schedule
Next wipe
2d 20h
Fri 16 Oct, 19:26 UTC
Group limit
trio
players per team
Gather rate
2x
read from the name
Score
0
player hours, last seven days
Map
3500
Procedural Map · seed 491950183
First seen
20 Sep 2026
no hostname published

Players

AveragePeak
00.250.50.75100:0009:0018:0003:0012:0021:00

Hourly average and peak, UTC. Busiest hour of the two days: 1 players.

Server performance

02040608000:0009:0018:0003:0012: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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep29 Sep4 Oct8 Oct13 Oct

Top 69% of all ranked servers, top 93% in EA, and #488 of the trio servers (top 82%). Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag
Next wipeFriday 16 October, 19:26 UTCin 2d 20h

Its weekly schedule tag · low confidence

usual gap
8.2 days
between real wipes
wipe-day peak
2
players, last three wipes
crowd held
0%
else halves by day 3

Coming wipes

  1. 2d 20hFri 16 Oct, 19:26 UTC
  2. 9d 20hFri 23 Oct, 19:26 UTC
  3. 16d 20hFri 30 Oct, 19:26 UTC
  4. 22d 19hThu 5 Nov, 19:00 UTCFW
  5. 23d 20hFri 6 Nov, 19:26 UTC
  6. 30d 20hFri 13 Nov, 19:26 UTC
  7. 37d 20hFri 20 Nov, 19:26 UTC
  8. 44d 20hFri 27 Nov, 19:26 UTC

The first 48 hours of its last wipes

Fri 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, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 19:26 UTC11d ago 1 – running 0
Thu 24 Sep, 14:15 UTC19d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Zev | Зэвэрсэн Тал | Mongolia 2x Modded | WeeklyEA · trio · 2x · weekly · 3 on average2/50+2
2WARBANDITS.GG SEA 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDEA · trio · 2x · weekly · 1 on average0/100−1
3『可乐』10.13/5倍/养老/三人/萌新礼包EA · trio · weekly · 28 on average7/100−22−75.6%
4WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPEDEA · trio · 3x · weekly · 5 on average4/100+4
5小海螺10.13号|14点新档|三人游玩EA · trio · weekly · 68 on average48/300+26+118.2%
6[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/07EA · trio · weekly · 49 on average0/180−4−100.0%

Quick answers

from the figures on this page

Rules & Settings

How is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours configured in terms of rules and settings?

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours carries its gather rate in its name: 2x. trio caps groups at 3 players. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. It uses the term vanilla for itself: no altered rates, kits or rules: the game as Facepunch ships it. The server has VAC, Valve's anti-cheat, switched on.

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

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours uses a procedural map of size 3,500 with seed 491950183, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Activity

What position does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hold in the server rankings?

On seven-day player hours, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sits at #15,485, in the top 69% across ranked servers and #488 in Asia. Among servers in trio, it stands at #488.

How full is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

0 of 150 slots on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours are filled at the moment. The mean over the last seven days is 0 players, reaching 1 at its highest. At 13:00 UTC in the last 48 hours, it averaged 0 players, the busiest hour.

Wipe Frequency

What can you expect on wipe day for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

An average of 2 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Below half by day 3 is where the crowd fell when it did not hold.

On what cycle does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe?

Its tag guides the prediction, as [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours has too few wipes on record to confirm its schedule. The date of its next wipe is Friday 16 October at 19:26 UTC. 11 days 3 hours ago the current world was created. The tags give a weekly wipe.

Server Info

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

In Asia, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself with the EA tag. Rust Analytics reports the location a server claims, not the machine's actual location. 167.104.102.100:28015 is its address.

What is the performance like on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Average server fps for the last 48 hours is 29; the floor was 8. At its peak it held 64,736 entities: buildings, deployables and the rest of the world. Memory use peaked at 4,417 MB. A climbing entity count plus low fps is the lag players report.

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

Rust network protocol 2634 and build 166586 on Linux is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs. Joining requires the same protocol on your game, which Steam updates.

Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours up, and how consistent is its uptime?

The server is live: [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. Its own uptime figure dates the last restart to roughly 11 days 1 hours ago. 100% is its uptime for the last 7 full days, 168 of 168 hours. The earliest Rust Analytics saw it was 20 September 2026.

Server Tags

What is the meaning of the tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Published by [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp150 (Max players): Slot count: 150; ts3 (Group limit): Teams take no more than 3; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166586 (Build): It runs build 166586; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^w (Weekly): Wipes land every week; ^v (Vanilla): No altered rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; EA (East Asia): The browser places this server in East Asia. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours show up in Rust Analytics lists and filters?

On Rust Analytics, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours matches these lists: 2x Rust servers, Modded Rust servers and Trio Rust servers. It appears under these filters 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 2 weeks; Gather rate: 2x.

Connection

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

The console route: start Rust, press F1, enter client.connect 167.104.102.100:28015. The page's Launch Rust button opens Rust through Steam and connects you instead. You can reach its website at https://discord.com/invite/6DAQjtGZD6.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp150
Max players Slot count: 150.
ts3
Group limit Teams take no more than 3.
v2634
Protocol Protocol 2634: matching game versions are required to join.
cs166586
Build It runs build 166586.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code No region code has been set.

Wipe schedule

^w
Weekly Wipes land every week.

Difficulty

^v
Vanilla No altered rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

Region

EA
East Asia The browser places this server in 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.