Online 139.180.188.139:28015 checked 9m ago

[SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP

3x weekly wipes moddedoxide

Connect

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

Launch Rust and join

Right now

srv.summary()

players now 0/200 # 0% full

7-day average 0 # peak 1

rank #13,662 # top 61%

last wipe 2d ago # weekly schedule

next wipe 4d 17h # Tue 3 Nov, 12:44 UTC

Players

srv.players.plot(range="48h")

AveragePeak

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")

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 9 Oct. 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

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Tuesday 3 November, 12:44 UTC, in 4d 17h. # Its weekly schedule tag · low confidence

usual gap8.6 daysbetween real wipes

on rhythm0%of its recent wipes

wipe-day peak1players, last three wipes

crowd held0%else halves by day 1

Coming wipes

	in	at	kind
0	4d 17h	Tue 3 Nov, 12:44 UTC	wipe
1	6d 23h	Thu 5 Nov, 19:00 UTC	FW force wipe
2	11d 17h	Tue 10 Nov, 12:44 UTC	wipe
3	18d 17h	Tue 17 Nov, 12:44 UTC	wipe
4	25d 17h	Tue 24 Nov, 12:44 UTC	wipe
5	32d 17h	Tue 1 Dec, 12:44 UTC	wipe
6	34d 23h	Thu 3 Dec, 19:00 UTC	FW force wipe
7	39d 17h	Tue 8 Dec, 12:44 UTC	wipe

The first 48 hours of its last wipes

Tue 27 OctTue 20 OctSat 10 Oct

Players each hour, from the hour of the wipe. The latest peaked at 1, 46 hours in.

Wipes · newest first

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
0	Tue 27 Oct, 12:44 UTC2d ago	1	NaN	running	0
1	Tue 20 Oct, 19:08 UTC9d ago	2	halved by day 1	6.7 days	0
2	Sat 10 Oct, 05:47 UTC19d ago	1	halved by day 1	10.6 days	1

# 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 1970586274

Map of [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP

map: Procedural Map
size: 3500
seed: 1970586274

Open on RustMaps

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 139.180.188.139:28015
region: –
max players: 200
group limit: 8, the default
wipe schedule: weekly
last wipe: 27 Oct 2026, 12:44 UTC
hostname: –
first seen: 9 Oct 2026

About this server · in its own words

print(srv.description)

Welcome to 1WIN SEA 5X | MAX 8! - 5x Gather Rates - TP & Home: /tpr /home /sethome - Rank for Kits - Instant Crafting - 5x Components & Scrap - Loot++ - 5x Stack Sizes - Barrels Drop More Loot - Max Group / Clan Size: 8 - Clan System & Clan Chat - Blueprint Share (Clan) - Vending Always In Stock - Faster Recyclers + Auto Barrel Pickup - Longer Days, Shorter Nights - Reduced Bed/Bag Cooldowns Direct Connect: 139.180.188.139:28015

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

rust.similar(srv).head(6)

	server	like_this	players
0	Japan Tokyo - Limited Raid Hours \|3x\|PvP\|JP	EA · groups of 8+ · 3x · weekly · 40 on average	3/300
1	SIX-SEVEN 67 \| Max 8 \| SEA \| Kits \| Shop \| 3X \| Wiped 10/28	EA · groups of 8+ · 3x · weekly · 1 on average	2/150
2	Jumprust.com - RustyIron 3x\|JP/SEA\|Full PVP\|Shop\|Kits\|Long	EA · groups of 100+ · 3x · monthly · 7 on average	8/120
3	ASIA \| RPG · Skills · NEW \| Casual PvP \| 2-5x \| Wiped 10/22	EA · groups of 8+ · 5x · weekly · 3 on average	0/120
4	\|TW-JP-SEA\|Rustyafied 2X Vanilla\|MAP WIPE 10/23	EA · groups of 12+ · 2x · weekly · 2 on average	1/200
5	HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP	EA · groups of 8+ · 3x · monthly · 2 on average	1/75

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP rank?

Player hours over seven days put [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP at #13,662, in the top 61% of the ranked set.

What population does [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP carry?

Current row: 0 players on [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP, against 200 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 14:00 UTC, mean 0 players.

About the server

How smoothly does [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP run?

Averaged over 48 hours: 234 server fps, never under 223. Buildings, deployables and all else in the world took the count as high as 66,599 entities. The memory field tops out at 1,891 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP?

Rust network protocol 2635 and build 168909 on Linux is what [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP, and is it up?

The current sample puts [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP online. A restart about 2 days 4 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 9 October 2026.

Where does [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP sit?

The name of [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP points to Asia, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 139.180.188.139:28015 is its address.

Settings and map

What rules and settings are recorded for [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP?

3x gather is what the name states, and the name is [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. The VAC field reads off.

What is the map on [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP?

[SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP runs a procedural map of size 3,500 with seed 1970586274, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP wipe, and how often?

Too few wipes are on record for [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP to confirm its schedule, so the tag drives the prediction. On Tuesday 3 November at 12:44 UTC the next wipe is due. The world it runs now was generated 2 days 6 hours ago. Its tags carry a weekly wipe schedule.

On [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP, what happens on wipe day?

The average peak over recent wipes is 1 players. 46 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Tags, lists

Which lists on Rust Data hold [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP, and which filters?

The Rust Data lists that [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP fits are: Modded Rust servers and 3x Rust servers, filtered live. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 3x.

Which meanings do the tags on [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP hold?

These tags are published by [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^w (Weekly): Wipes run weekly; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join [SEA] 888 3x Server |Solo/Duo/Trio/Quad/Max5|Loot+|TP?

In Rust, F1 opens the console: type client.connect 139.180.188.139:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp200,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z

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.