A10/ 200 players
Modded#15,966
[JPN]1919810
Online 203.10.98.3:28015 checked 10m ago
biweekly wipes
moddedoxide
players now0of 100 slots
7-day average0peak –
rank#15,966top 72%
last wipe · restocked8d agobiweekly schedule
next wipe · restock5d 2hMon 19 Oct, 10:33 UTC
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
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 7 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestRankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Monday 19 October, 10:33 UTC, in 5d 2h. 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A213/ 200 players
A32/ 200 players
B13/ 200 players
B21/ 60 players
B31/ 100 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
How should you read the tags on [JPN]1919810?
gmvanilla (Game mode): Vanilla survival mode; mp100 (Max players): The cap is 100; ts6 (Group limit): A team holds 6 at most; v2634 (Protocol): Protocol 2634: your game must match to get in; cs166652 (Build): It runs on build 166652; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): It sits in Modded: plugins or settings make the difference is what [JPN]1919810 tags itself with, and the server browser takes note. Tags also carry its current players, its queue and when the world was made, all up top on this page.
On Rust Vending Machine, which lists and filters can you find [JPN]1919810 in?
These Rust Vending Machine 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; Last wipe: In the last 2 weeks.
Settings and rules
Which map is currently on [JPN]1919810?
A procedural map, size 4,000 with seed 265649668, generated by the game, is what [JPN]1919810 runs. From this page you can look at it on RustMaps: 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. The group size is capped at 6 players. This server runs survival, the usual game of gathering, building and raiding. You can fight and raid other players. Plugins or settings change the game, so it is listed under Modded. You will find Oxide plugins running here. The server has VAC, Valve's anti-cheat, switched on.
Server info
What location is [JPN]1919810 in?
You will find no region published for [JPN]1919810. Rust Vending Machine reports the location a server claims, not where the machine actually sits. You can reach it at 203.10.98.3:28015.
What is the uptime like on [JPN]1919810?
You can grab [JPN]1919810: it is online as we speak. Its uptime figure puts the last restart at roughly 40 hours ago. Across the last 6 days, it was available for 144 of 144 hours, or 100% of the time. Its first record on Rust Vending Machine is dated 7 October 2026.
Is [JPN]1919810 lag-free?
The 48-hour average for server fps is 59, and the floor was 57. The entity count reached 88,228: that includes buildings, deployables and everything else. Memory use peaked at 3,069 MB. What players call lag comes from low fps and an entity count on the rise.
Which Rust build is [JPN]1919810 running?
On Windows, [JPN]1919810 is running Rust network protocol 2634 and build 166652. To get in, your game must match the protocol; Steam keeps that updated.
Player count
How does [JPN]1919810 compare to other Rust servers in the rankings?
Over the last seven days [JPN]1919810 ranks #15,966 on player hours, among the top 72% of all ranked servers.
How many players are on [JPN]1919810 right now?
[JPN]1919810 is carrying 0 players on 100 slots at the moment. The seven-day average stands at 0 players.
Wipe details
How often does [JPN]1919810 wipe?
The estimate of [JPN]1919810's next wipe comes from biweekly: 14 days after its last wipe. It is due to wipe next on Monday 19 October at 10:33 UTC. The world it has now started 8 days 21 hours ago. A wipe every two weeks is published in its tags.
Join the server
What is the way to join [JPN]1919810?
Open Rust and press F1 for the console, then type client.connect 203.10.98.3:28015. Or use the Launch Rust button here to open the game through Steam and connect. The web address is https://www.youtube.com/watch?v=k-6O8gGbdz0.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^b,gmvanilla,cs166652,ts6,^o^z
Game
gmvanilla
Game mode Vanilla survival mode.
mp100
Max players The cap is 100.
ts6
Group limit A team holds 6 at most.
v2634
Protocol Protocol 2634: your game must match to get in.
cs166652
Build It runs on build 166652.
ptrak
Networking The game's usual network layer, RakNet, is used.
$r?
Region code No region code is set.
Wipe schedule
^b
Biweekly Two-week wipe cycle.
Mods and access
^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded It sits in Modded: plugins or settings make the difference.
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.