Skip to the story

Live edition72,372 playing on 11,823 servers

Rust Insights

Server profile · EA

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

Online, with 0 of 150 players on; ranked #14,648 of every public Rust server, the top 66%. It last wiped 6d ago.

Filed under 2x trio weekly wipes vanillamoddedoxide
Launch Rust and join Website
0/ 150 players now 0% full
07-day averagepeak 1
#14,648ranktop 66% · #477 in EA
6d agolast wipeweekly schedule
19hnext wipeFri 30 Oct, 09:25 UTC

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
0123414:0023:0008:0017:0003:0012:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

02040608014:0023:0008:0017:0003:0012:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

The wipe cycle

Wipe schedule

From its schedule tag.

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

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

Coming wipes

  1. 19hFri 30 Oct, 09:25 UTC
  2. 7d 5hThu 5 Nov, 19:00 UTCFW
  3. 7d 19hFri 6 Nov, 09:25 UTC
  4. 14d 19hFri 13 Nov, 09:25 UTC
  5. 21d 19hFri 20 Nov, 09:25 UTC
  6. 28d 19hFri 27 Nov, 09:25 UTC
  7. 35d 5hThu 3 Dec, 19:00 UTCFW
  8. 35d 19hFri 4 Dec, 09:25 UTC

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

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

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

The record

Wipes

Every wipe we saw, newest first.

WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 09:25 UTC6d ago 1 – running 0
Fri 2 Oct, 19:26 UTC26d ago 1 halved by day 2 20.6 days 0
Thu 24 Sep, 14:15 UTC34d ago 2 halved by day 3 8.2 days 0

Note: 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.

If you like this one

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Zev | Зэвэрсэн Тал | Mongolia 2x Modded | WeeklyEA · trio · 2x · weekly · 2 on average0/50
  2. QS『可乐』10.28/5倍/养老/三人/萌新礼包EA · trio · weekly · 22 on average1/100
  3. WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPEDEA · trio · 3x · weekly · 3 on average5/100
  4. [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/28EA · trio · weekly · 116 on average177/200
  5. 小海螺10.28号|14点新档|三人游玩EA · trio · weekly · 29 on average9/300
  6. 『元宇宙』10.27号新开/独狼/三人/萌新服EA · trio · weekly · 26 on average1/200

The short version

Quick answers

From the figures on this page.

Wipe schedule

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

Recent wipes peaked at 1 players on average. 5 hours after the latest wipe, the crowd peaked. In 0% of recent wipes, more than half the peak was still playing at the next wipe. In the other cases, it dropped below half by day 2.5.

How often does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe, and on which day?

The prediction for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours follows its tag, because too few of its wipes are on record to confirm the schedule. A wipe is expected on Friday 30 October at 09:25 UTC. 6 days 4 hours have passed since its current world was created. The tags list wipes as weekly.

Server

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

Server fps averaged 49 over 48 hours; the lowest reading was 22. The world held a peak of 67,228 entities, counting buildings, deployables and all the rest. The highest memory figure was 2,378 MB. Lag, for players, is low fps and an entity count that keeps climbing.

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

The Rust build is network protocol 2635 and build 168909, running on Linux, for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. You can only join if your game is on the same protocol; Steam handles that update.

What does uptime look like for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and is it online?

Right now [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is up and running. About 15 hours ago is when it last restarted, judged from the uptime it reports. It spent 167 of the last 7 full days' 168 hours up, 99% of the time. Rust Insights first logged this server on 20 September 2026.

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

With its EA tag, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself in Asia. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 167.104.102.100:28015 is where it answers.

Server tags

What is meant by each tag on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

When the game's server browser reads [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp150 (Max players): It holds 150 slots; ts3 (Group limit): Team size is capped at 3; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): The region code field is empty; ^w (Weekly): Wipes arrive weekly; ^v (Vanilla): Facepunch's game as shipped: rates, kits and rules are unchanged; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded is its listing, because plugins or settings change how the game plays; EA (East Asia): Its browser listing sits under East Asia. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

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

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appears among the following Rust Insights lists: Rust servers with a 2x gather rate, Modded Rust servers, explained and Best trio Rust servers. On the server list, the filters that surface it are 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

How many players are on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours right now, and how does that number move?

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours shows 0 players at the moment, against 150 slots. A weekly average of 0 players goes with a peak of 1.

How does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours compare with other Rust servers in the ranking?

In Asia, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is #477; across all ranked servers it is #14,648 on seven-day player hours, in the top 66%. In the trio category it ranks #501.

Map and rules

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

The name of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours says 2x gather. A group may hold up to 3 players, listed as trio. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, so it sits under Modded in the browser. Plugins: Oxide run here. The server describes itself as vanilla, meaning facepunch's game as shipped: rates, kits and rules are unchanged. The server has Valve's VAC anti-cheat switched on.

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

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs a procedural map of size 3,500 with seed 272704469, generated by the game. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.

Join

How can you get onto [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Open the console with F1 in Rust and enter client.connect 167.104.102.100:28015. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you. Its website can be found at https://discord.com/invite/6DAQjtGZD6.

The small print

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 It holds 150 slots.
ts3
Group limit Team size is capped at 3.
v2635
Protocol Matching versions are required, and the protocol is 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking Rust's standard network layer, RakNet, carries it.
$r?
Region code The region code field is empty.

Wipe schedule

^w
Weekly Wipes arrive weekly.

Difficulty

^v
Vanilla Facepunch's game as shipped: rates, kits and rules are unchanged.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded is its listing, because plugins or settings change how the game plays.

Region

EA
East Asia Its browser listing sits under East Asia.

Note: 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.