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
52/ 100
D
Moving up: up 748 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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.
No daily history yet.
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
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 7 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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Monday 2 November, 10:33 UTC, in 5d 14h.
Biweekly: 14 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region is published for [JPN]1919810. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 203.10.98.2:28015.
How reliable is [JPN]1919810, and is it up?
The server is down: [JPN]1919810 is offline now, with the last sighting 20 days 14 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 7 October 2026, Rust Server Score saw it for the first time.
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
How frequently does [JPN]1919810 wipe its map?
biweekly: 14 days after its last wipe gives the basis for estimating [JPN]1919810's next wipe. It is due to wipe next on Monday 2 November at 10:33 UTC. The world it runs now was created 22 days 9 hours. Its tags say it wipes every two weeks.
Population
Where does [JPN]1919810 sit among Rust servers?
In the top 71% of all ranked servers, [JPN]1919810 sits at #15,961 for player hours over the last seven days.
How many players does [JPN]1919810 usually have?
The last sighting of [JPN]1919810 was 20 days 14 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on [JPN]1919810?
The game's browser takes its cue from the tags [JPN]1919810 has set: gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): The server holds 100 slots; ts6 (Group limit): No team may go above 6; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
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
How is [JPN]1919810 set up, and what rules does it keep?
You will find no gather rate in the name of [JPN]1919810. A group here can reach 6 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on [JPN]1919810?
The game generates the procedural map on [JPN]1919810 at size 4,000 with seed 265649668. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto [JPN]1919810?
Enter client.connect 203.10.98.2:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. 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 modeYou play vanilla survival here.
mp100
Max playersThe server holds 100 slots.
ts6
Group limitNo team may go above 6.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Strongest in momentum (D); standing is the one to work on (F).