Rust Data LabData lab · live
Live readings Servers11,750 Players59,433 Populated3,457 Fresh wipes · 3h137 Sampled every 5 min

Element card · group Vanilla · atomic number 14,699, its rank

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

Online EA 167.104.102.100:28015 checked 8m ago

2x trio weekly wipes vanillamoddedoxide
Join the experiment
Atomic mass · players now 0/ 150 0% full Room to join
7-day average0peak 1
Rank · atomic number#14,699top 66% · #494 in EA
Last wipe4d agoweekly schedule
Next wipe2d 10hFri 30 Oct, 09:25 UTC
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123400:0009:0018:0003:0012:0021:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
025507510000: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:25 UTC, in 2d 10h. 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 10hFri 30 Oct, 09:25 UTC
  2. 8d 19hThu 5 Nov, 19:00 UTCFW
  3. 9d 10hFri 6 Nov, 09:25 UTC
  4. 16d 10hFri 13 Nov, 09:25 UTC
  5. 23d 10hFri 20 Nov, 09:25 UTC
  6. 30d 10hFri 27 Nov, 09:25 UTC
  7. 36d 19hThu 3 Dec, 19:00 UTCFW
  8. 37d 10hFri 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.

Reaction 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ze Zev | Зэвэрсэн… 0
    Zev | Зэвэрсэн Тал | Mongolia 2x Modded | Weekly EA · trio · 2x · weekly · 2 on average 0/ 50
  2. 2 Qs QS『可乐』10.27/5倍… 8
    QS『可乐』10.27/5倍/养老/三人/萌新礼包 EA · trio · weekly · 21 on average 8/ 100
  3. 3 Wa WARBANDITS.GG … 3
    WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPED EA · trio · 3x · weekly · 3 on average 3/ 100
  4. 4 So [JP/Tokyo] SOR… 0
    [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 EA · trio · weekly · 41 on average 0/ 180
  5. 5 元宇 『元宇宙』10.27号新开/… 4
    『元宇宙』10.27号新开/独狼/三人/萌新服 EA · trio · weekly · 30 on average 4/ 200
  6. 6 大世 『大世界』10.25号/新开… 0
    『大世界』10.25号/新开/三人行/萌新入门服 EA · trio · weekly · 26 on average 0/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

A procedural map of size 3,500 with seed 272704469 runs on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, generated by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

How is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours configured, and what rules apply?

According to its name, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs 2x gather. A group can hold 3 players at most (trio). survival is the game mode, raiding, building and gathering: the standard game. Raids and player fights are part of play here. Plugins or settings change the game, so the browser lists it under Modded. Plugins in use: Oxide. By its own description it is vanilla: nothing is changed: rates, kits and rules are as Facepunch ships them. Anti-cheat is on: Valve's VAC.

Server facts

In what location does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sit?

The EA tag is how [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself, in Asia. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 167.104.102.100:28015.

What Rust version does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours currently run?

Rust network protocol 2635 and build 168909 on Linux is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours for staying online?

At the moment, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. The uptime it reports suggests it restarted roughly 4 minutes ago. For the last 7 full days, 168 of 168 hours were online, giving 100% uptime. It first appeared to Rust Data Lab on 20 September 2026.

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

Server fps averaged 47 over the last 48 hours, with 12 as the lowest. The entity count reached 66,918, including buildings, deployables and all other world items. Memory use peaked at 2,335 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe schedule

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

Its tag guides the prediction, since [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's record holds too few wipes to confirm a schedule. The wipe after this one is due on Friday 30 October at 09:25 UTC. Counting back, the current world began 4 days 13 hours ago. Its tags carry a weekly wipe schedule.

What does a typical wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours involve?

Averaged across its recent wipes, the busiest point drew 1 players. 5 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 0% of its recent wipes. Where it did not hold, the crowd dropped below half by day 2.5.

Where it appears

What should you understand from the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours carries?

These are the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp150 (Max players): Player slots: 150; ts3 (Group limit): No team may exceed 3; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^w (Weekly): A wipe comes every week; ^v (Vanilla): Nothing is changed: rates, kits and rules are as Facepunch ships them; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; EA (East Asia): East Asia is where the browser lists this server. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear in?

The Rust Data Lab lists that include [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours are: 2x gather rate servers, Modded Rust servers, measured and Trio Rust servers, measured live. 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.

Player numbers

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

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is #14,699 on seven-day player hours, #494 in Asia, and in the top 66% of all ranked servers. Within trio, its rank is #507.

How many players does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours have at the moment?

At the moment [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours has 0 of its 150 slots filled. A seven-day sample gives 0 players on average and 1 at the top.

How to join

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

You can connect by pressing F1 in Rust and entering client.connect 167.104.102.100:28015, or by pressing Launch Rust here, which starts the game through Steam and joins for you. You can find its website at https://discord.com/invite/6DAQjtGZD6.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp150
Max players Player slots: 150.
ts3
Group limit No team may exceed 3.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Wipe schedule

^w
Weekly A wipe comes every week.

Difficulty

^v
Vanilla Nothing is changed: rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.
^z
Modded You will find it under Modded: the game is altered by plugins or settings.

Region

EA
East Asia East Asia is where the browser lists this server.

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.