Working its way up from the back of the class: #15,411 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
49/ 100
D
Slipped a little: down 238 places this week. Nothing a good wipe can't fix.
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.
AveragePeak
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
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 20 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
In what location does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 sit?
No region tag appears for [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 31.214.142.68:10900.
How reliable is [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24, and is it up?
The server is down: [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is offline now, with the last sighting 8 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 20 October 2026.
Which Rust version is [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 running?
The server [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 wipe, and how often?
[JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 27 days 22 hours.
Player numbers
Where does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 place in the wider field of Rust servers?
Over the last seven days, [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 has #15,411 for player hours, in the top 69% of all ranked servers.
What does the population on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 look like?
It has been 8 days 6 hours since [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?
The game's browser takes its cue from the tags [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 has set: gmvanilla (Game mode): You play vanilla survival here; mp105 (Max players): Its slot count is 105; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?
Rust Server Score lists that include [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24: Rust servers for beginners, graded and Best community servers, graded. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 set up, and what rules does it keep?
Nothing in the name of [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?
A procedural map of size 4,000 and seed 2026680033, generated by the game, is what [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?
Enter client.connect 31.214.142.68:10900 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://discord.com/invite/CptKMHfmm.
Server tags
what each one means
Published asmp105,ptrak,$r?,v2634,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp105
Max playersIts slot count is 105.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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).