Working its way up from the back of the class: #15,961 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 9,193 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Monday 2 November, 10:33 UTC, in 5d 0h.
Its biweekly schedule tag · low confidence
wipe-day peak3players, last three wipes
Coming wipes
5d 0hMon 2 Nov, 10:33 UTC
8d 8hThu 5 Nov, 19:00 UTCFW
19d 0hMon 16 Nov, 10:33 UTC
33d 0hMon 30 Nov, 10:33 UTC
36d 8hThu 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
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 10:33 UTC22d 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
classmates: the same kind of game, then region, group limit, rate and wipes
[JPN]1919810 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 203.10.98.63:28015 is the address to use.
How reliable is [JPN]1919810, and is it up?
The server is down: [JPN]1919810 is offline now, with the last sighting 21 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 5 October 2026.
What Rust version is [JPN]1919810 on?
Rust network protocol 2634 and build 166652 on Windows is what [JPN]1919810 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does [JPN]1919810 wipe, and how often?
Too few wipes on [JPN]1919810 are recorded to confirm the schedule, so its tag guides the prediction. Monday 2 November at 10:33 UTC is the date set for its next wipe. The world it runs now was created 22 days 23 hours. A fortnightly wipe schedule appears in its tags.
What happens on [JPN]1919810 when wipe day arrives?
Recent wipes have peaked at 3 players on average. Peak numbers came 1 hours into the latest wipe.
Player numbers
Where does [JPN]1919810 place in the wider field of Rust servers?
Over the last seven days, [JPN]1919810 has #15,961 for player hours, in the top 71% of all ranked servers.
How many players does [JPN]1919810 usually have?
[JPN]1919810 is offline at the moment; the last time it was seen was 21 days 5 hours ago.
Tags
What do [JPN]1919810's tags stand for?
You'll see [JPN]1919810 tagged with gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): The server holds 100 slots; ts6 (Group limit): A team can hold 6 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [JPN]1919810?
These Rust Server Score lists count [JPN]1919810 among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Map and rules
What settings and rules apply on [JPN]1919810?
Nothing in the name of [JPN]1919810 states a gather rate. The limit for a group is 6 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
[JPN]1919810 runs which map?
A procedural map of size 4,000 and seed 265649668, generated by the game, is what [JPN]1919810 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto [JPN]1919810?
To connect, start Rust, press F1, and type client.connect 203.10.98.63:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://www.youtube.com/watch?v=k-6O8gGbdz0.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^b,gmvanilla,cs166652,ts6,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersThe server holds 100 slots.
ts6
Group limitA team can hold 6 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
A term to build on. Even marks across the subjects, from F to F.