[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours
EA 167.104.102.100:28015 checked 11m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 69% of all ranked servers, top 94% in EA, and #496 of the trio servers (top 82%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 16 October, 19:26 UTC, in 2d 5h. 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
- 2d 5hFri 16 Oct, 19:26 UTC
- 9d 5hFri 23 Oct, 19:26 UTC
- 16d 5hFri 30 Oct, 19:26 UTC
- 22d 5hThu 5 Nov, 19:00 UTCFW
- 23d 5hFri 6 Nov, 19:26 UTC
- 30d 5hFri 13 Nov, 19:26 UTC
- 37d 5hFri 20 Nov, 19:26 UTC
- 44d 5hFri 27 Nov, 19:26 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 19:26 UTC 11d ago | 1 | – | running | 0 |
| Thu 24 Sep, 14:15 UTC 19d 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
Quick answers
Player Count
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sit in the rankings?
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours ranks #492 in Asia and #15,431 overall on player hours over the last seven days, in the top 69% of ranked servers. Within the trio group, it is #496.
Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours busy?
The current player count for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is 0, out of 150 slots. The seven-day average player count stands at 0, and the highest point was 1. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 0 players.
Tags & Lists
What is the meaning of the tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
For [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, the game's server browser reads the following tags: gmrust (Game mode): Standard survival gameplay; mp150 (Max players): Slots: 150; ts3 (Group limit): 3 is the largest team allowed; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs166586 (Build): Running build 166586; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code missing; ^w (Weekly): Wipes happen weekly; ^v (Vanilla): No changed rates, kits or rules—the game as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded, because plugins or settings modify play; EA (East Asia): In the server browser it appears under East Asia. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours in BestRustServers.xyz lists and filters: which ones?
These BestRustServers.xyz lists include [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: Rust servers with 2x gather rate, Best modded Rust servers and Trio servers (group limit 3). On the server list, the filters that bring it up 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 2 weeks; Gather rate: 2x.
Server Details
What Rust version is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on?
Rust network protocol 2634 and build 166586 on Linux is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours uses. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours smooth?
For the past 48 hours, server fps averaged 30, never dropping below 8. It held up to 64,736 entities: everything from buildings to deployables in the world. The maximum memory used was 4,469 MB. A climbing entity count and low fps are felt by players as lag.
What is the uptime and reliability of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
The server is online: [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. The uptime it reports shows a restart roughly 11 days 16 hours ago. Over the past 7 full days, it was online 168 of 168 hours, 100% of the time. On 20 September 2026, BestRustServers.xyz saw it for the first time.
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours location: where is it?
In Asia, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself with its EA tag. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. You can reach it at 167.104.102.100:28015.
Settings & Map
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours map: which one is it?
A procedural map of size 3,500 and seed 491950183 is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours rules and settings: what are they?
2x gather: that is the rate [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours states in its name. The group limit stands at 3 players, listed as trio. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. The Modded section of the browser holds it: plugins or settings apply. Plugin count: Oxide. Self-described as vanilla: no changed rates, kits or rules—the game as shipped. VAC: on.
Wipe Information
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe schedule: what does it show?
As [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's record holds too few wipes to confirm its schedule, its tag drives the prediction. Friday 16 October at 19:26 UTC is when the next wipe is due. The current world has been running since 11 days 18 hours. The tags state a weekly wipe cycle.
What happens on wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
The average busiest point of its recent wipes was 2 players. 0 hours into the latest wipe, the crowd reached its peak. The crowd held above half the peak until the next wipe in 0% of recent wipes. When it fell, the crowd dropped under half by day 3.
Connect
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours joining: how is it done?
To connect, type client.connect 167.104.102.100:28015 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you. You can find its website at https://discord.com/invite/6DAQjtGZD6.
Server tags
Published as mp150,ptrak,$r?,v2634,^w,^v,EA,gmrust,cs166586,ts3,^o^z
Game
gmrust- Game mode Standard survival gameplay.
mp150- Max players Slots: 150.
ts3- Group limit 3 is the largest team allowed.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs166586- Build Running build 166586.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code missing.
Wipe schedule
^w- Weekly Wipes happen weekly.
Difficulty
^v- Vanilla No changed rates, kits or rules—the game as shipped.
Mods and access
^o- Oxide Plugin framework: Oxide (uMod).
^z- Modded Under Modded, because plugins or settings modify play.
Region
EA- East Asia In the server browser it appears 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.