Skip to the page
Network live 11,755 servers online 61,286 players aboard 124 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online EA 167.104.102.100:28015 checked 13m ago

2x trio weekly wipes vanillamoddedoxide
Tracking number · connect
Wipe progress · wiped 4d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Fri 30 Oct, 09:25 UK Fri 30 Oct, 09:25 UTC in 2d 10h · low confidence
0/ 150 players now 0% full
07-day averagepeak 1
#14,699ranktop 66% · #494 in EA
4d agolast wipeweekly schedule
2d 10hnext wipeFri 30 Oct, 09:25 UTC
Delivery history

Players, performance and rank

Players

AveragePeak
0123400:0009:0018:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

025507510000:0009:0018:0003:0012:0021: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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule

from its schedule tag
Next delivery expected

Next wipe Friday 30 October, 09:25 UTC · 09:25 UK, in 2d 10h.

Its weekly schedule tag · low confidence
14.4 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 2.5

Coming wipes

  1. 2d 10hFri 30 Oct, 09:25 UTC09:25 UK
  2. 8d 19hThu 5 Nov, 19:00 UTC19:00 UKFW
  3. 9d 10hFri 6 Nov, 09:25 UTC09:25 UK
  4. 16d 10hFri 13 Nov, 09:25 UTC09:25 UK
  5. 23d 10hFri 20 Nov, 09:25 UTC09:25 UK
  6. 30d 10hFri 27 Nov, 09:25 UTC09:25 UK
  7. 36d 19hThu 3 Dec, 19:00 UTC19:00 UKFW
  8. 37d 10hFri 4 Dec, 09:25 UTC09:25 UK

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

every wipe as a delivery, newest first
  1. Fri 30 Oct, 09:25 UTC09:25 UK · in 2d 10h
    Next wipe expected · its weekly schedule tag
  2. Fri 23 Oct, 09:25 UTC 10:25 UK · 4d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Fri 2 Oct, 19:26 UTC 20:26 UK · 25d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 2
    Lasted
    20.6 days
    Players before
    0
  4. Thu 24 Sep, 14:15 UTC 15:15 UK · 33d ago
    Wipe delivered
    Peak
    2
    Crowd
    halved by day 3
    Lasted
    8.2 days
    Players before
    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 parcels

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 average 0 / 50
  2. QS『可乐』10.27/5倍/养老/三人/萌新礼包EA · trio · weekly · 21 on average 8 / 100
  3. WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPEDEA · trio · 3x · weekly · 3 on average 3 / 100
  4. [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21EA · trio · weekly · 41 on average 0 / 180
  5. 『元宇宙』10.27号新开/独狼/三人/萌新服EA · trio · weekly · 30 on average 4 / 200
  6. 『大世界』10.25号/新开/三人行/萌新入门服EA · trio · weekly · 26 on average 0 / 200
Help desk

Quick answers

From the figures on this page.

Population

What is the ranking of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours against other Rust servers?

On player hours over the last seven days, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours ranks #14,699 overall and #494 in Asia, in the top 66% of all ranked servers. Ranked against other trio servers, it comes in at #507.

Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours busy at the moment?

Checking now: 0 players on 150 slots at [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. Averaged over the past week: 0 players, peaking at 1.

Map and rules

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

Generated by the game with seed 272704469, the procedural map on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is size 3,500. You can see the map on RustMaps from this page, since one size and seed give one map.

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

Gather rate on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is 2x, as its name says. The cap on a group is 3 players (trio). You get survival here, the usual game: build, gather, raid. Raiding and PvP are both on. Because plugins or settings change the game, it is filed under Modded in the server browser. Oxide supplies the plugins. The vanilla label is one it applies to itself: played as Facepunch ships it, with rates, kits and rules unchanged. VAC, Valve's anti-cheat, is switched on.

Server details

What location does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours run from?

Its EA tag puts [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours in Asia. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 167.104.102.100:28015 is its address.

Does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours perform well?

Server fps over the last 48 hours averaged 47; the lowest was 12. Buildings, deployables and all the rest of the world pushed its entity count as high as 66,918. The highest memory reading was 2,335 MB. Lag, to players, means low fps alongside an entity count on the rise.

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

Right now, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. Its reported uptime suggests a restart roughly 4 minutes ago. It was up 168 of 168 hours over the last 7 full days, 100% of the time. The first sighting of it by Rust Wipe Tracker came on 20 September 2026.

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

The version on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is Rust network protocol 2635 and build 168909, running on Linux. The same protocol is required to join, and Steam takes care of updating it.

Wipe schedule

How does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours handle its wipe days?

1 players is the average peak across its recent wipes. On the latest wipe, 5 hours passed before the crowd peaked. Half the peak or more was held until the next wipe in 0% of recent wipes. By day 2.5 it had fallen below half where the crowd did not hold.

When does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe? What schedule does it follow?

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. Friday 30 October at 09:25 UTC is when its next wipe is due. You are playing a world created 4 days 13 hours. The tags state that it wipes each week.

Tags and listings

On Rust Wipe Tracker, which lists and filters is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours part of?

You will find [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on the following Rust Wipe Tracker lists: Rust servers with a 2x gather rate, Modded Rust servers and Trio Rust servers, max team of 3. You will find it 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 the meaning of the server tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

Read off the game's server browser, the tags for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours are: gmrust (Game mode): Survival in standard Rust; mp150 (Max players): Slot count: 150; ts3 (Group limit): The team limit is 3; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^w (Weekly): A wipe every week; ^v (Vanilla): Played as Facepunch ships it, with rates, kits and rules unchanged; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; EA (East Asia): Server browser category: East Asia. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Connecting

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

Enter client.connect 167.104.102.100:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. Its website can be found at https://discord.com/invite/6DAQjtGZD6.

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 standard Rust.
mp150
Max players Slot count: 150.
ts3
Group limit The team limit is 3.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly A wipe every week.

Difficulty

^v
Vanilla Played as Facepunch ships it, with rates, kits and rules unchanged.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.

Region

EA
East Asia Server browser category: 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.