[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours
Online EA 167.104.102.100:28015 checked 13m ago
Server instruments
last reading Tue 19:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 12 · below 20 is lag, below 10 is badEntities
48 h range 53,178–66,918 · memory 2,335 MBUptime
22 h 4 min since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 66% of all ranked servers, top 91% in EA, and #506 of the trio servers (top 80%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 09:25 UTC, in 2d 13h. Its weekly schedule tag · low confidence
Coming wipes
- WPT 1Fri 30 Oct, 09:25 UTC2d 13h
- WPT 2Thu 5 Nov, 19:00 UTC8d 22hFW
- WPT 3Fri 6 Nov, 09:25 UTC9d 13h
- WPT 4Fri 13 Nov, 09:25 UTC16d 13h
- WPT 5Fri 20 Nov, 09:25 UTC23d 13h
- WPT 6Fri 27 Nov, 09:25 UTC30d 13h
- WPT 7Thu 3 Dec, 19:00 UTC36d 22hFW
- WPT 8Fri 4 Dec, 09:25 UTC37d 13h
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
newest first| Wiped | Peak | Crowd | Lasted | Players 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/50
- 23/100
- 1/100
- 2/180
- 4/200
- 0/200
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
At their busiest, its recent wipes drew 1 players on average. 5 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 2.5 it fell below half.
How often does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe, and when?
Its tag guides the prediction: too few of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's wipes are on record to confirm its schedule. Friday 30 October at 09:25 UTC is when its next wipe is due. The world it runs now was made 4 days 10 hours ago. Its tags carry a weekly wipe schedule.
Lists and filters
How should you read the tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Tags published by [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): 150 slots in total; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^w (Weekly): It wipes each week; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): The server browser files it under East Asia. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours appear in Rust Metrics lists and filters?
These Rust Metrics lists carry [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. Check: filters. On the server list it appears under these: 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.
Occupancy
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sit in the rankings?
Top 66% of all ranked servers: [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours takes #14,680 on seven-day player hours and #495 in Asia. Among servers in trio, it stands at #506.
What is the population on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
0 of 150 slots are filled on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours right now. Check: players over seven days. Average 0, peak 1.
Server details
What location is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hosted in?
Reading: location. The EA tag puts [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 167.104.102.100:28015.
What Rust version is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on?
Rust network protocol 2635 and build 168909 on Linux is the build [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs. Matching protocol is required to join. Let Steam update your game.
How does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours perform?
Over the last 48 hours the average was 46 server fps; the floor was 12. Peak entity count: 66,918. Buildings, deployables and all else included. Reading: 2,335 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
How reliable is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and is it online now?
Check: connection. [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online at this moment. Reading: uptime. About 22 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 20 September 2026.
Settings and map
How is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours configured, and what rules are in force?
Gather rate check: 2x. That comes from the name [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. Groups stop at 3 players. The label given is trio. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Check: map. Procedural, size 3,500, seed 272704469, generated by the game on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
What do you do to join [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
To join: start Rust, press F1 and type client.connect 167.104.102.100:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/6DAQjtGZD6.