On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,373top 69%
Last wipe23d agobiweekly schedule
Next wipe4d 15hMon 2 Nov, 10:33 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,373 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
98/ 100
A+
Runs smoothly: 59 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
48/ 100
D
Slipped a little: down 709 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (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
No five-minute samples in the last two hours.
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 best
RankRank in region
Top 69% 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 4d 15h.
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
You won't find a region tag on [JP]真夏の夜のらんらんるー, but its name indicates Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 203.10.98.3:28015.
How reliable is [JP]真夏の夜のらんらんるー, and is it up?
Right now, [JP]真夏の夜のらんらんるー is online. According to its reported uptime, the last restart was about 4 days 1 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 7 October 2026, Rust Server Score saw it for the first time.
Is [JP]真夏の夜のらんらんるー smooth to play on?
The average over the last 48 hours was 59 server fps, and it never went below 59. At its peak, it held 88,230 entities, including buildings, deployables and all else in the world. At its highest, it used 3,890 MB of memory. When fps is low and entities climb, that is lag to players.
What Rust version is [JP]真夏の夜のらんらんるー on?
You will find [JP]真夏の夜のらんらんるー on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does [JP]真夏の夜のらんらんるー wipe, and how often?
The next wipe on [JP]真夏の夜のらんらんるー is a projection from biweekly: 14 days after its last wipe. Monday 2 November at 10:33 UTC is the date set for its next wipe. The world it runs now was created 23 days 8 hours. Its tags say it wipes every two weeks.
Player numbers
Where does [JP]真夏の夜のらんらんるー place in the wider field of Rust servers?
Over the last seven days, [JP]真夏の夜のらんらんるー has #15,373 for player hours, in the top 69% of all ranked servers.
Is [JP]真夏の夜のらんらんるー a busy server?
Right now, 0 players are on [JP]真夏の夜のらんらんるー, which has 100 slots. Over the past seven days, the average player count was 0.
Tags and filters
What do [JP]真夏の夜のらんらんるー's tags stand for?
The game's browser takes its cue from the tags [JP]真夏の夜のらんらんるー has set: gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts6 (Group limit): Teams cap out at 6; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [JP]真夏の夜のらんらんるー appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [JP]真夏の夜のらんらんるー: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; 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 [JP]真夏の夜のらんらんるー set up, and what rules does it keep?
Nothing in the name of [JP]真夏の夜のらんらんるー states a gather rate. You can play in groups of up to 6 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [JP]真夏の夜のらんらんるー uses?
The game generates the procedural map on [JP]真夏の夜のらんらんるー at size 4,000 with seed 265649668. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join [JP]真夏の夜のらんらんるー?
Enter client.connect 203.10.98.3: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://www.youtube.com/watch?v=G6N943NlCbw.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^b,gmvanilla,cs166652,ts6,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts6
Group limitTeams cap out at 6.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxideThe plugin framework in use is 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).