Rust Server Analytics 76,398 players11,761 servers
All servers
Drill-through Server detail

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

Online EA 167.104.102.100:28015 checked 9m ago

Drill-through
FilterServeris [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Ra…
Attributes
2x trio weekly wipes vanillamoddedoxide
Last refreshed
Players now 0/ 150
7-day average 0 peak 1
Rank #14,742 top 66% · #494 in EA
Last wipe 5d ago weekly schedule
Next wipe 1d 19h Fri 30 Oct, 09:25 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123414:0023:0008:0018:0003:0012:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
025507510014:0023:0008:0018:0003:0012: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:25 UTC, in 1d 19h. 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

InWhen, UTCKind
1d 19hFri 30 Oct, 09:25 UTCits own
8d 5hThu 5 Nov, 19:00 UTCFW force wipe
8d 19hFri 6 Nov, 09:25 UTCits own
15d 19hFri 13 Nov, 09:25 UTCits own
22d 19hFri 20 Nov, 09:25 UTCits own
29d 19hFri 27 Nov, 09:25 UTCits own
36d 5hThu 3 Dec, 19:00 UTCFW force wipe
36d 19hFri 4 Dec, 09:25 UTCits own

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 09:25 UTC5d 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
ServerProfilePlayers now
Zev | Зэвэрсэн Тал | Mongolia 2x Modded | Weekly EA · trio · 2x · weekly · 2 on average 3 / 50
QS『可乐』10.28/5倍/养老/三人/萌新礼包 EA · trio · weekly · 21 on average 29 / 100
WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPED EA · trio · 3x · weekly · 3 on average 3 / 100
[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/28 EA · trio · weekly · 120 on average 191 / 200
『元宇宙』10.27号新开/独狼/三人/萌新服 EA · trio · weekly · 27 on average 3 / 200
『大世界』10.28号/18:00新开/三人行/萌新入门服 EA · trio · weekly · 25 on average 154 / 200

Quick answers

from the figures on this page

Wipe data

The wipe schedule for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: what is it?

The tag sets the prediction: too few of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's wipes are on record to confirm its schedule. A wipe is scheduled for Friday 30 October at 09:25 UTC, according to this server's cycle. The current world dates from 5 days 4 hours. Its tags carry a weekly wipe schedule.

Wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: what should you expect?

Across recent wipes the busiest point averaged 1 players. 5 hours after the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The fall below half arrived by day 2.5 when it didn't hold.

Server

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

Its EA tag puts [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours in Asia. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 167.104.102.100:28015.

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

The platform is Linux, with Rust network protocol 2635 and build 168909 running on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. Joining requires the same protocol on your game; Steam handles the update.

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

As of the latest refresh, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. About 15 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 100%, or 168 of 168 hours. It entered Rust Server Analytics records on 20 September 2026.

What performance does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours show?

The 48-hour average was 51 server fps; the low was 28. Buildings, deployables and all other world objects brought the entity total to 66,967. Memory use reached 2,335 MB at peak. Players experience lag as low fps combined with a rising entity count.

Tags

What do [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's tags stand for?

The game's server browser reads the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours publishes: gmrust (Game mode): Survival in the standard Rust format; mp150 (Max players): 150 slots in total; ts3 (Group limit): The cap is 3 players per team; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^w (Weekly): The server wipes each week; ^v (Vanilla): Stock Facepunch settings, with no rate changes, kits or extra rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing, where plugins or settings change the game; EA (East Asia): East Asia is the region it appears under in the browser. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: Rust servers with a 2x gather rate, Modded Rust servers: live data and Trio Rust servers, 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.

Population

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

For player hours over the last seven days, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours places #14,742 globally and #494 in Asia, in the top 66% of all ranked servers. The trio segment places it at #505.

How many players does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours carry?

Population at the current refresh: 0 players on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, against 150 slots. The seven-day mean is 0 players, against a peak of 1.

Map and rules

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

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours names a 2x gather rate. Up to 3 players can form a group (trio). It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Modded category lists it; plugins or settings change the game. Oxide plugins are run. Vanilla is its own description: stock Facepunch settings, with no rate changes, kits or extra rules. VAC, Valve's anti-cheat, is enabled.

The map on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: which one is it?

The game generates a procedural map of size 3,500 with seed 272704469 for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. The map is reproducible from its size and seed and can be seen on RustMaps from here.

How to join

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

In the Rust console (F1), enter client.connect 167.104.102.100:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://discord.com/invite/6DAQjtGZD6 is its website.

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 the standard Rust format.
mp150
Max players 150 slots in total.
ts3
Group limit The cap is 3 players per team.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Wipe schedule

^w
Weekly The server wipes each week.

Difficulty

^v
Vanilla Stock Facepunch settings, with no rate changes, kits or extra rules.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing, where plugins or settings change the game.

Region

EA
East Asia East Asia is the region it appears under in the browser.

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.