Station XX-15961 · no signal
[JPN]1919810
Offline 203.10.98.63:28015 checked 21d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,961
- top 71%
- Last wipe
- 23d ago
- biweekly schedule
- Next wipe
- 4d 14h
- Mon 2 Nov, 10:33 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Monday 2 November, 10:33 UTC, in 4d 14h. Its biweekly schedule tag · low confidence
- wipe-day peak
- 3players, last three wipes
Coming wipes
- 4d 14hMon 2 Nov, 10:33 UTC
- 7d 22hThu 5 Nov, 19:00 UTCFW
- 18d 14hMon 16 Nov, 10:33 UTC
- 32d 14hMon 30 Nov, 10:33 UTC
- 35d 22hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 10:33 UTC23d ago | M0.5▲rising | 3 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [JPN]1919810?
The procedural map on [JPN]1919810 is size 4,000 with seed 265649668, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [JPN]1919810?
The name of [JPN]1919810 gives no gather rate. 6 players is the most a group can hold. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on [JPN]1919810 right now?
No players are recorded on [JPN]1919810 at this moment; it is offline, and the last sighting was 21 days 15 hours ago.
How does [JPN]1919810 rank against other Rust servers?
On player hours for the past week, [JPN]1919810 sits at #15,961, which puts it inside the top 71% of every ranked server.
Operator and location
How reliably does [JPN]1919810 stay online?
No contact with [JPN]1919810 right now, and the last recorded contact was 21 days 15 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 5 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is [JPN]1919810 hosted?
A region is not published by [JPN]1919810. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 203.10.98.63:28015.
Which Rust version is [JPN]1919810 running?
On Windows, [JPN]1919810 runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on [JPN]1919810?
The recent wipes averaged a busiest count of 3 players. The peak on the most recent wipe came 1 hours after the wipe.
How often does [JPN]1919810 wipe, and on which days?
Its schedule cannot be confirmed, as too few of [JPN]1919810's wipes are on record; the prediction follows its tag instead. Monday 2 November at 10:33 UTC is when its next wipe is due. 23 days 9 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Tags
What do the server tags on [JPN]1919810 mean?
The game's server browser reads the tags [JPN]1919810 publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp100 (Max players): The server has 100 slots; ts6 (Group limit): The team limit is 6; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does [JPN]1919810 appear?
You will find [JPN]1919810 on the following Rust Server Trends lists: Modded Rust servers, tracked live. 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.
Join the server
How do you connect to [JPN]1919810?
You can connect by pressing F1 in Rust and typing client.connect 203.10.98.63:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://www.youtube.com/watch?v=k-6O8gGbdz0 is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.