Rust Data

rustdata.spaceservers167.104.102.100:28017.ipynb

Run all rust-data · live

‹ All servers

Online EA 167.104.102.100:28015 checked 8m ago

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

2x trio weekly wipes vanillamoddedoxide

Connect

srv = rust.server("167.104.102.100:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/150 # 0% full
7-day average 0 # peak 1
rank #14,698 # top 66% · #495 in EA
last wipe 4d ago # weekly schedule
next wipe 2d 11h # Fri 30 Oct, 09:25 UTC

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510023:0008:0017: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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

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

usual gap14.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5

Coming wipes

inatkind
02d 11hFri 30 Oct, 09:25 UTCwipe
18d 20hThu 5 Nov, 19:00 UTCFW force wipe
29d 11hFri 6 Nov, 09:25 UTCwipe
316d 11hFri 13 Nov, 09:25 UTCwipe
423d 11hFri 20 Nov, 09:25 UTCwipe
530d 11hFri 27 Nov, 09:25 UTCwipe
636d 20hThu 3 Dec, 19:00 UTCFW force wipe
737d 11hFri 4 Dec, 09:25 UTCwipe

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 · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 09:25 UTC4d ago 1 NaN running 0
1 Fri 2 Oct, 19:26 UTC25d ago 1 halved by day 2 20.6 days 0
2 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.

display(srv.map, srv.info())

Map

3500 · seed 272704469
Map of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours
map
Procedural Map
size
3500
seed
272704469
Open on RustMaps

Server

srv.info()
address
167.104.102.100:28015
region
EA
max players
150
group limit
trio
wipe schedule
weekly
last wipe
23 Oct 2026, 09:25 UTC
hostname
–
first seen
20 Sep 2026

About this server · in its own words

print(srv.description)
Singapore Solo/Duo/Trio (MAX3) 2x Vanilla+. Player-base raid protection 00:00-10:00 SGT; public raid bases stay raidable. 2x gather & loot, instant craft except explosives, 1.5x smelting, 5-minute nights. Fresh wipe: 23 Oct. Next wipe: 30 Oct, 03:00 SGT. Discord: https://discord.gg/6DAQjtGZD6

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Zev | Зэвэрсэн Тал | Mongolia 2x Modded | WeeklyEA · trio · 2x · weekly · 2 on average2/50
1QS『可乐』10.27/5倍/养老/三人/萌新礼包EA · trio · weekly · 21 on average8/100
2WARBANDITS.GG SEA 3X |Solo/Duo/Trio|LootX3| JUST WIPEDEA · trio · 3x · weekly · 3 on average4/100
3[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21EA · trio · weekly · 41 on average1/180
4『元宇宙』10.27号新开/独狼/三人/萌新服EA · trio · weekly · 30 on average5/200
5『大世界』10.25号/新开/三人行/萌新入门服EA · trio · weekly · 26 on average0/200

Quick answers

From the figures on this page.

Population

How does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours compare in the rankings?

Player hours over the last seven days: #14,698 for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, #495 in Asia, within the top 66% of the ranked set. The trio group places it at #506.

How many players does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hold at once?

Current row: 0 players on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, against 150 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

How smoothly does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours run?

Averaged over 48 hours: 47 server fps, never under 12. Buildings, deployables and all else in the world took the count as high as 66,918 entities. Memory peaked at 2,335 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. Steam updates your game for you, but the protocol must match to join.

How reliable is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and is it online now?

The current sample puts [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours online. The uptime it reports puts the last restart about 4 minutes ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 20 September 2026.

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

With its EA tag, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours lists itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 167.104.102.100:28015.

Rules, settings, map

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

Gather sits at 2x, read from the server's own name: [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours. trio sets the cap: 3 players per group. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.

Which map has [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours loaded?

[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs a procedural map of size 3,500 with seed 272704469, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

On what schedule does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours wipe?

Too few wipes are on record for [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours to confirm its schedule, so the tag drives the prediction. On Friday 30 October at 09:25 UTC the next wipe is due. A new world was started 4 days 12 hours ago, and that is the one in play. Its tags carry a weekly wipe schedule.

What is wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours like?

The average peak over recent wipes is 1 players. 5 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.5.

Lists and tags

Which lists on Rust Data hold [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and which filters?

The Rust Data lists that [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours fits are: Modded Rust servers, 2x Rust servers and Trio Rust servers. Under these filters on the server list, it is listed: 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.

Which meanings do the tags on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours hold?

Read by the game's server browser, the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours publishes are: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): The server lists 150 slots; ts3 (Group limit): The team cap is 3; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^w (Weekly): Wipes run weekly; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?

The manual route: launch Rust, F1, then client.connect 167.104.102.100:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/6DAQjtGZD6 is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp150,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts3,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp150
Max players The server lists 150 slots.
ts3
Group limit The team cap is 3.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^w
Weekly Wipes run weekly.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EA
East Asia The server browser files it 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.

Rust Data 65,657 players 11,832 servers online