[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours
Online EA 167.104.102.100:28015 checked 9m 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 66% of all ranked servers, top 88% in EA, and #506 of the trio servers (top 81%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 09:25 UTC, in 1d 5h. Its weekly schedule tag · low confidence
- usual gap
- 14.4 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 2.5
Coming wipes
- in 1d 5hFri 30 Oct, 09:25 UTC
- in 7d 15hThu 5 Nov, 19:00 UTCFW
- in 8d 5hFri 6 Nov, 09:25 UTC
- in 15d 5hFri 13 Nov, 09:25 UTC
- in 22d 5hFri 20 Nov, 09:25 UTC
- in 29d 5hFri 27 Nov, 09:25 UTC
- in 35d 15hThu 3 Dec, 19:00 UTCFW
- in 36d 5hFri 4 Dec, 09:25 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
23 OCT 2026Fri 23 Oct, 09:25 UTC5d ago |
1 | – | running | 0 |
2 OCT 2026Fri 2 Oct, 19:26 UTC26d ago |
1 | halved by day 2 | 20.6 days | 0 |
24 SEP 2026Thu 24 Sep, 14:15 UTC34d 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.
Quick answers
From the figures on this page.
Rules and settings
On [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, which rules and settings apply?
By its name, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours gathers at 2x. The server sets a group limit of 3 players (trio). Filed under survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. Its own label is vanilla: no changed rates, kits or rules: this is the game Facepunch ships. VAC, Valve's anti-cheat, is enabled.
What is the map on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Size 3,500, seed 272704469: the game generates the procedural map on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. From this page you can view the map on RustMaps; the same size and seed give the same map.
Lists and filters
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear among the Rust Server Index lists and filters?
These lists on Rust Server Index take [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: Rust servers filed under 2x gather rate, Modded Rust servers, filed by play style and Trio servers, filed under group limit. Filed 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 week; Gather rate: 2x.
What is meant by the tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Filed under these tags, as published by [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp150 (Max players): The queue ceiling sits at 150; ts3 (Group limit): 3 is the largest team allowed; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): It runs build 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): The region code field is left empty; ^w (Weekly): Wipes run on a weekly cycle; ^v (Vanilla): No changed rates, kits or rules: this is the game Facepunch ships; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Modded: the game is changed by plugins or settings; EA (East Asia): The browser files it under East Asia. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe dates
What should you expect on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. 5 hours into the latest wipe, the crowd reached its peak. Its recent wipes kept the crowd above half the peak until the next wipe 0% of the time. By day 2.5 the crowd had fallen below half when it didn't hold.
How often is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wiped, and on what schedule?
The prediction follows its tag, because too few of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's wipes are on record to confirm the schedule. Dated for Friday 30 October at 09:25 UTC: its next wipe. Its present world dates from 5 days 18 hours. A weekly wipe schedule is published in its tags.
Players and ranking
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sit in the rankings?
On seven-day player hours, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours takes #14,683 overall and #493 in Asia, within the top 66% of ranked servers. Among servers in the trio group, the rank is #506.
What does the player count on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours look like?
The live count for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours stands at 0 players, out of 150 slots. Filed under seven-day figures: an average of 0 players and a peak of 1.
Server facts
Which Rust build is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours running?
Rust network protocol 2635 and build 168909, on Linux, is what [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs. The protocol must match before you can join, and Steam takes care of updating it.
How reliable is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and is it online now?
You will find [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours online as of now. The uptime it reports puts the last restart at about 5 hours ago. Uptime for the last 7 full days came to 99%, 167 hours out of 168. The earliest sighting at Rust Server Index is 20 September 2026.
Is the performance on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours good?
Server fps held at 49 on average across the last 48 hours, never dropping below 36. The entity count reached 66,997, covering buildings, deployables and all else in the world. Memory use reached as much as 2,335 MB. A climbing entity count and low fps are felt by players as lag.
What is the location of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours gives Asia as its location and the tag EA. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 167.104.102.100:28015.
Connecting
How can you connect to [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Two ways in. Type client.connect 167.104.102.100:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. https://discord.com/invite/6DAQjtGZD6 is where its website lives.
Server tags
What each one means.
Published as mp150,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts3,^o^z
Game
gmrust
mp150
ts3
v2635
cs168909
ptrak
$r?
Wipe schedule
^w
Difficulty
^v
Mods and access
^o
^z
Region
EA
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.