On the class lists: C (62), with population over 48 hours and no performance mark.
Players now4/ 607% full
7-day average5peak 16
Rank#1,336top 6%
Last wipe27d agomonthly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
9/ 100
F
A quiet classroom so far: 5 of 60 on average. Plenty of space to grow.
Standingrank on player hours
94/ 100
A
Well up the rankings: #1,336 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
62/ 100
C
Slows down under load at times: 37 server fps on average.
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 57 places this week.
A fair term, with more to come.
Strongest in uptime (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 6% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h.
The force wipe · high confidence
wipe-day peak24players, last three wipes
Coming wipes
7d 11hThu 5 Nov, 19:00 UTCFW
35d 11hThu 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 24, 32 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 23:39 UTCFW27d ago
24
–
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
Which region is [JP][PVE][BP]もちもちRUST SERVER 10/2~ based in?
You won't find a region tag on [JP][PVE][BP]もちもちRUST SERVER 10/2~, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 210.131.222.67:28015 is the address to use.
How reliable is [JP][PVE][BP]もちもちRUST SERVER 10/2~, and is it up?
The server is up: [JP][PVE][BP]もちもちRUST SERVER 10/2~ is online now. The uptime it reports puts the last restart at about 2 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does [JP][PVE][BP]もちもちRUST SERVER 10/2~ run?
It never fell below 1 server fps in the last 48 hours, averaging 37. At its peak, it held 152,002 entities, including buildings, deployables and all else in the world. Up to 4,873 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does [JP][PVE][BP]もちもちRUST SERVER 10/2~ sit?
Rust network protocol 2635 and build 168909 on Linux is what [JP][PVE][BP]もちもちRUST SERVER 10/2~ runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [JP][PVE][BP]もちもちRUST SERVER 10/2~ reset?
Once a month, [JP][PVE][BP]もちもちRUST SERVER 10/2~ wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 27 days 6 hours have passed since this world was made. The tags show a monthly wipe schedule.
What should you expect from wipe day on [JP][PVE][BP]もちもちRUST SERVER 10/2~?
Across its recent wipes, the busiest moments averaged 24 players. Peak numbers came 32 hours into the latest wipe.
Player count
Where does [JP][PVE][BP]もちもちRUST SERVER 10/2~ place in the wider field of Rust servers?
Over the last seven days, [JP][PVE][BP]もちもちRUST SERVER 10/2~ has #1,336 for player hours, in the top 6% of all ranked servers.
Is [JP][PVE][BP]もちもちRUST SERVER 10/2~ a busy server?
Right now, 4 players are on [JP][PVE][BP]もちもちRUST SERVER 10/2~, which has 60 slots. Averaging 5 players over seven days, it peaked at 16. Over the last 48 hours, the peak hour was 12:00 UTC, averaging 12 players.
Tags
How should you read the tags on [JP][PVE][BP]もちもちRUST SERVER 10/2~?
You'll see [JP][PVE][BP]もちもちRUST SERVER 10/2~ tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp60 (Max players): 60 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [JP][PVE][BP]もちもちRUST SERVER 10/2~ appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP][PVE][BP]もちもちRUST SERVER 10/2~ among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
How is [JP][PVE][BP]もちもちRUST SERVER 10/2~ set up, and what rules does it keep?
You will find no gather rate in the name of [JP][PVE][BP]もちもちRUST SERVER 10/2~. The default of 8 players applies as the group cap. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [JP][PVE][BP]もちもちRUST SERVER 10/2~ uses?
The game generates the procedural map on [JP][PVE][BP]もちもちRUST SERVER 10/2~ at size 4,500 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Getting in
How do you get onto [JP][PVE][BP]もちもちRUST SERVER 10/2~?
Enter client.connect 210.131.222.67:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/z9AK9EFwSG.
Server tags
what each one means
Published asmp60,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp60
Max players60 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).