Rust Data

rustdata.spaceservers114.34.55.63:28018.ipynb

Run all rust-data · live

‹ All servers

Offline EA 114.34.55.63:28016 checked 20d ago

台灣服10月2日

biweekly wipes oxide

Connect

srv = rust.server("114.34.55.63:28018")
print(srv.connect_command)

Right now

srv.summary()
players now 0/150 # 0% full
7-day average 0 # peak –
rank #15,829 # top 72% · #489 in EA
last wipe 26d ago # biweekly schedule
next wipe 1d 10h # Fri 30 Oct, 11:21 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 17 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 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

Top 72% of all ranked servers, top 94% in EA. Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Friday 30 October, 11:21 UTC, in 1d 10h. # Its biweekly schedule tag · low confidence

usual gap15 daysbetween real wipes
wipe-day peak28players, last three wipes
crowd held0%else halves by day 4

Coming wipes

inatkind
01d 10hFri 30 Oct, 11:21 UTCwipe
17d 18hThu 5 Nov, 19:00 UTCFW force wipe
215d 10hFri 13 Nov, 11:21 UTCwipe
329d 10hFri 27 Nov, 11:21 UTCwipe
435d 18hThu 3 Dec, 19:00 UTCFW force wipe
543d 10hFri 11 Dec, 11:21 UTCwipe

The first 48 hours of its last wipes

Fri 2 OctThu 17 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 26, 45 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 11:21 UTC26d ago 26 NaN running 0
1 Thu 17 Sep, 12:32 UTC41d ago 30 halved by day 4 15 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

4500 · seed 4500
Map of 台灣服10月2日
map
Procedural Map
size
4500
seed
4500
Open on RustMaps

Server

srv.info()
address
114.34.55.63:28016
region
EA
max players
150
group limit
8, the default
wipe schedule
biweekly
last wipe
2 Oct 2026, 11:21 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 66 on average4/200
1Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 42 on average14/215
2Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 27 on average5/100
3[SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 4 on average0/200
4JP ONLY 2WEEK SOLO/DUO/TORIO#84EA · groups of 8+ · biweekly · 3 on average1/60
5[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average1/100

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does 台灣服10月2日 rank?

On seven-day player hours 台灣服10月2日 is #15,829 overall and #489 in Asia, inside the top 72% of all ranked servers.

What population does 台灣服10月2日 carry?

The current row shows 台灣服10月2日 offline; the last response was 20 days 6 hours ago.

Server facts

What Rust version does 台灣服10月2日 run?

The build is Rust network protocol 2634 and build 167058 on Windows, run by 台灣服10月2日. The protocol has to match before you can join, and Steam does the updating.

How reliable is 台灣服10月2日, and is it online now?

台灣服10月2日 is offline at this refresh; the last response came 20 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does 台灣服10月2日 run from?

With its EA tag, 台灣服10月2日 lists itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 114.34.55.63:28016.

Rules, settings, map

What rules and settings are recorded for 台灣服10月2日?

You will not find a gather rate in the string 台灣服10月2日. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. The plugin count is Oxide. Anti-cheat status: VAC on.

What is the map on 台灣服10月2日?

The game generates the map on 台灣服10月2日: procedural, size 4,500, seed 4500. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does 台灣服10月2日 wipe, and on what schedule?

The tag sets the prediction: 台灣服10月2日 has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Friday 30 October at 11:21 UTC. This world was created 26 days 13 hours ago. The tags list a two-weekly wipe cycle.

What is wipe day on 台灣服10月2日 like?

Across recent wipes the busiest point averaged 28 players. Peak population on the latest wipe came 45 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 4 in the other cases.

Lists and tags

Which Rust Data filters and lists contain 台灣服10月2日?

On Rust Data, 台灣服10月2日 appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

How should you read the server tags on 台灣服10月2日?

These tags are published by 台灣服10月2日 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): 150 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): Build number: 167058; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Runs on Oxide (uMod) for plugins; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join 台灣服10月2日?

The manual route: launch Rust, F1, then client.connect 114.34.55.63:28016. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp150,ptrak,$r?,v2634,^b,EA,gmrust,cs167058,ts8,^o

Game

gmrust
Game mode Rust survival in its standard form.
mp150
Max players 150 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167058
Build Build number: 167058.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.

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 47,275 players 11,713 servers online