Rust Data

rustdata.spaceservers203.10.98.63:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 203.10.98.63:28015 checked 20d ago

[JPN]1919810

biweekly wipes moddedoxide

Connect

srv = rust.server("203.10.98.63:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,961 # top 71%
last wipe 22d ago # biweekly schedule
next wipe 5d 10h # Mon 2 Nov, 10:33 UTC
display(Image(srv.banner))

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 5 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
15k10k15k20k5 Oct7 Oct9 Oct10 Oct12 Oct14 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Monday 2 November, 10:33 UTC, in 5d 10h. # Its biweekly schedule tag · low confidence

wipe-day peak3players, last three wipes

Coming wipes

inatkind
05d 10hMon 2 Nov, 10:33 UTCwipe
18d 18hThu 5 Nov, 19:00 UTCFW force wipe
219d 10hMon 16 Nov, 10:33 UTCwipe
333d 10hMon 30 Nov, 10:33 UTCwipe
436d 18hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 10:33 UTC22d ago 3 NaN running 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

4000 · seed 265649668
Map of [JPN]1919810
map
Procedural Map
size
4000
seed
265649668
Open on RustMaps

Server

srv.info()
address
203.10.98.63:28015
region
–
max players
100
group limit
6 max
wipe schedule
biweekly
last wipe
5 Oct 2026, 10:33 UTC
hostname
–
first seen
5 Oct 2026

About this server · in its own words

print(srv.description)
全てのリソースとアイテムが二倍 (金属バネ.銃の本体.硫黃を除く) All Loot and Resource 2x (Except Spring/Gun body/Sulfur) /remove - 実体の削除,ビルダーによる2h時間以内の撤去が可能 Buildings can be demolished in two hours 地図リセット時間は木曜日の午後(1500-1900) ブループリントは、毎月第一木曜日の翌朝にリセットされます Map wipe time is every Thursday (1500-1900) Blueprint wipe time is the day after the first Thursday of every month /krhelp - Shows all commands in chat

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

rust.similar(srv).head(6)
serverlike_thisplayers
0PRIME RUST Х5 MAX5 ДЛЯ НОВИЧКОВEU · groups of 5 · biweekly · 1 on average1/200
1[LATAM] www.pandarust.ar Vanilla | WIPE 22/10 17hsSA · groups of 5 · biweekly · 59 on average42/200
2Rusty Moose |US Low|NA · groups of 6 · biweekly · 25 on average17/200
3『百威』无商城|无权|六人|10.27号14:00清档EA · groups of 6 · biweekly · 13 on average12/100
4[JP]初心者 | momoserver | 10/16 | PVPEA · groups of 6 · biweekly · 11 on average1/60
5Rusty Moose |EU Low|EU · groups of 6 · biweekly · 4 on average7/200

Quick answers

From the figures on this page.

Population data

What position does [JPN]1919810 take in the server rankings?

Over the last seven days [JPN]1919810 sits at #15,961 on player hours, in the top 71% of ranked servers.

How full does [JPN]1919810 run?

[JPN]1919810 returns no live count at this refresh, having last been seen 20 days 19 hours ago.

Server facts

Which Rust version is [JPN]1919810 on?

The build is Rust network protocol 2634 and build 166652 on Windows, run by [JPN]1919810. Steam updates your game for you, but the protocol must match to join.

Is [JPN]1919810 up, and what does its uptime show?

Offline now for [JPN]1919810, last seen 20 days 19 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 5 October 2026.

Which location does [JPN]1919810 run from?

For [JPN]1919810, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 203.10.98.63:28015 is its address.

Map and rules

Which rules apply on [JPN]1919810, and what settings?

You will not find a gather rate in the string [JPN]1919810. The cap on a group is 6 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has [JPN]1919810 loaded?

[JPN]1919810 runs a procedural map of size 4,000 with seed 265649668, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does [JPN]1919810 wipe?

The tag sets the prediction: [JPN]1919810 has too few wipes on record to confirm its schedule. On Monday 2 November at 10:33 UTC the next wipe is due. A new world was started 22 days 13 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.

What is wipe day on [JPN]1919810 like?

Recent wipes averaged 3 players at their peak. Peak population on the latest wipe came 1 hours in.

Tags and filters

Which lists on Rust Data hold [JPN]1919810, and which filters?

These Rust Data lists include [JPN]1919810: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Which meanings do the tags on [JPN]1919810 hold?

The game's server browser reads these tags from [JPN]1919810: gmvanilla (Game mode): Survival in vanilla form; mp100 (Max players): The server lists 100 slots; ts6 (Group limit): No team may exceed 6; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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

How can I connect to [JPN]1919810?

The manual route: launch Rust, F1, then client.connect 203.10.98.63:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://www.youtube.com/watch?v=k-6O8gGbdz0 is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,^b,gmvanilla,cs166652,ts6,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp100
Max players The server lists 100 slots.
ts6
Group limit No team may exceed 6.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build The server runs build 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Mods and access

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

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 51,860 players 11,711 servers online