On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 600% full
7-day average9peak 42
Rank#1,019top 5%
Last wipe12d agobiweekly schedule
Next wipe1d 12hFri 30 Oct, 12:36 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
15/ 100
F
A quiet classroom so far: 9 of 60 on average. Plenty of space to grow.
Standingrank on player hours
95/ 100
A+
Well up the rankings: #1,019 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
100/ 100
A+
Runs smoothly: 91 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 187 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); wipes are 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 5% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
····W··
·······
····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 Friday 30 October, 12:36 UTC, in 1d 12h.
Its biweekly schedule tag · low confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak46players, last three wipes
crowd held0%else halves by day 9
Coming wipes
1d 12hFri 30 Oct, 12:36 UTC
7d 19hThu 5 Nov, 19:00 UTCFW
15d 12hFri 13 Nov, 12:36 UTC
29d 12hFri 27 Nov, 12:36 UTC
35d 19hThu 3 Dec, 19:00 UTCFW
43d 12hFri 11 Dec, 12:36 UTC
The first 48 hours of its last wipes
Fri 16 OctFri 2 OctFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 41, 27 hours in, with 3 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 12:36 UTC12d ago
41+3 queue
–
running
9
Fri 2 Oct, 11:18 UTC26d ago
48+1 queue
halved by day 7
14.1 days
0
Fri 18 Sep, 14:09 UTC40d ago
50+16 queue
halved by day 11
13.9 days
1
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]初心者 | momoserver | 10/16 | PVP based in?
No region tag appears for [JP]初心者 | momoserver | 10/16 | PVP, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. 118.27.225.83:28015 is the address to use.
How reliable is [JP]初心者 | momoserver | 10/16 | PVP, and is it up?
Right now, [JP]初心者 | momoserver | 10/16 | PVP is online. About 8 hours ago, it restarted, based on the uptime it reports. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does [JP]初心者 | momoserver | 10/16 | PVP perform well?
It never fell below 62 server fps in the last 48 hours, averaging 91. Up to 107,265 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,868 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does [JP]初心者 | momoserver | 10/16 | PVP sit?
Rust network protocol 2635 and build 168909 on Linux is what [JP]初心者 | momoserver | 10/16 | PVP runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [JP]初心者 | momoserver | 10/16 | PVP reset?
Its tag sets the prediction, as the record holds too few of [JP]初心者 | momoserver | 10/16 | PVP's wipes to confirm its schedule. It is due to wipe next on Friday 30 October at 12:36 UTC. 12 days 11 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on [JP]初心者 | momoserver | 10/16 | PVP?
Across its recent wipes, the busiest moments averaged 46 players. The latest wipe peaked 27 hours in, with 3 more players queued at that point. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 9.
Population
Where does [JP]初心者 | momoserver | 10/16 | PVP place in the wider field of Rust servers?
Over the last seven days, [JP]初心者 | momoserver | 10/16 | PVP has #1,019 for player hours, in the top 5% of all ranked servers.
What does the population on [JP]初心者 | momoserver | 10/16 | PVP look like?
Right now, 0 players are on [JP]初心者 | momoserver | 10/16 | PVP, which has 60 slots. Averaging 9 players over seven days, it peaked at 42. The busiest time in the last 48 hours was 12:00 UTC, with an average of 15 players.
Lists and filters
What do [JP]初心者 | momoserver | 10/16 | PVP's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp60 (Max players): Its slot count is 60; ts6 (Group limit): No team may go above 6; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight are the tags [JP]初心者 | momoserver | 10/16 | PVP publishes, and the game's server browser reads them. 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]初心者 | momoserver | 10/16 | PVP appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP]初心者 | momoserver | 10/16 | PVP among them: Best community servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Server rules
How is [JP]初心者 | momoserver | 10/16 | PVP set up, and what rules does it keep?
The name of [JP]初心者 | momoserver | 10/16 | PVP gives no gather rate. A group here can reach 6 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [JP]初心者 | momoserver | 10/16 | PVP uses?
[JP]初心者 | momoserver | 10/16 | PVP runs a game-generated procedural map at size 3,850, seed 663820083. 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 [JP]初心者 | momoserver | 10/16 | PVP?
To connect, start Rust, press F1, and type client.connect 118.27.225.83:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/Myze6ftUv4.
Server tags
what each one means
Published asmp60,ptrak,$r?,v2635,^b,gmrust,cs168909,ts6
Game
gmrust
Game modeSurvival in the standard Rust style.
mp60
Max playersIts slot count is 60.
ts6
Group limitNo team may go above 6.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
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 performance (A+); wipes are the one to work on (F).