Rust Server Analytics 66,491 players11,702 servers
All servers
Drill-through Server detail

[JPN]1919810

Offline 203.10.98.63:28015 checked 21d ago

Drill-through
FilterServeris [JPN]1919810
Attributes
biweekly wipes moddedoxide
Last refreshed
Players now 0/ 100
7-day average 0 peak –
Rank #15,961 top 71%
Last wipe 23d ago biweekly schedule
Next wipe 4d 22h Mon 2 Nov, 10:33 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
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
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

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

wipe-day peak3players, last three wipes

Coming wipes

InWhen, UTCKind
4d 22hMon 2 Nov, 10:33 UTCits own
8d 7hThu 5 Nov, 19:00 UTCFW force wipe
18d 22hMon 16 Nov, 10:33 UTCits own
32d 22hMon 30 Nov, 10:33 UTCits own
36d 7hThu 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
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 10:33 UTC23d ago 3 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
PRIME RUST Х5 MAX5 ДЛЯ НОВИЧКОВ EU · groups of 5 · biweekly · 1 on average 0 / 200
[LATAM] www.pandarust.ar Vanilla | WIPE 22/10 17hs SA · groups of 5 · biweekly · 59 on average 2 / 200
Rusty Moose |US Low| NA · groups of 6 · biweekly · 24 on average 7 / 200
『百威』无商城|无权|六人|10.28号14:00清档 EA · groups of 6 · biweekly · 13 on average 23 / 100
[JP]初心者 | momoserver | 10/16 | PVP EA · groups of 6 · biweekly · 10 on average 3 / 60
Rusty Moose |EU Low| EU · groups of 6 · biweekly · 6 on average 6 / 200

Quick answers

from the figures on this page

Wipe data

The wipe schedule for [JPN]1919810: what is it?

The tag sets the prediction: too few of [JPN]1919810's wipes are on record to confirm its schedule. A wipe is scheduled for Monday 2 November at 10:33 UTC, according to this server's cycle. 23 days 1 hours ago the current world was made. Its tags publish a wipe schedule of every two weeks.

On [JPN]1919810, what happens on wipe day?

Across recent wipes the busiest point averaged 3 players. The highest player count on the latest wipe arrived 1 hours in.

Server details

In which region does [JPN]1919810 sit?

A region is not published by [JPN]1919810. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 203.10.98.63:28015.

Which Rust version is [JPN]1919810 on?

Rust network protocol 2634 and build 166652 on Windows is the setup for [JPN]1919810. Your game must match the protocol to join, and Steam applies that update.

Is [JPN]1919810 up, and how steady is its uptime?

The current status is offline for [JPN]1919810, with the last sighting 21 days 7 hours ago. Uptime over the last full days (7) was 0%, or 0 of 168 hours. It entered Rust Server Analytics records on 5 October 2026.

Tags

How should the tags on [JPN]1919810 be read?

The game's server browser reads the tags [JPN]1919810 publishes: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): Player slots: 100; ts6 (Group limit): Team size is capped at 6; v2634 (Protocol): Joining needs your game on protocol 2634; cs166652 (Build): Build number 166652; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^b (Biweekly): A two-week wipe cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does [JPN]1919810 appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count [JPN]1919810 among their servers: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Player numbers

Where does [JPN]1919810 sit among Rust servers?

Player hours for the last seven days place [JPN]1919810 at #15,961, in the top 71% of the ranked field.

At what level does [JPN]1919810 run its population?

[JPN]1919810 is offline at this refresh; the last contact was 21 days 7 hours ago.

Settings

What settings and rules does [JPN]1919810 use?

The name of [JPN]1919810 does not state a gather rate. A maximum of 6 players per group applies. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.

The map on [JPN]1919810: which one is it?

[JPN]1919810 uses a procedural map of size 4,000 with seed 265649668, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

How do you connect to [JPN]1919810?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 203.10.98.63:28015. https://www.youtube.com/watch?v=k-6O8gGbdz0 is its website.

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players Player slots: 100.
ts6
Group limit Team size is capped at 6.
v2634
Protocol Joining needs your game on protocol 2634.
cs166652
Build Build number 166652.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly A two-week wipe cycle.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change 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.