On the class lists: B (75), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average4peak 11
Rank#1,559top 7%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
4/ 100
F
A quiet classroom so far: 4 of 100 on average. Plenty of space to grow.
Standingrank on player hours
93/ 100
A
Well up the rankings: #1,559 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: 73 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
81/ 100
B+
Climbing fast: up 959 places this week.
A good term.
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
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 7% 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
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap13.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak5players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Fri 23 OctFri 2 OctFri 25 Sep
Players each hour, from the hour of the wipe. The latest peaked at 8, 32 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 08:02 UTC6d ago
8
–
running
1
Fri 2 Oct, 11:13 UTC27d ago
3
✓ held half
20.9 days
0
Fri 25 Sep, 11:07 UTC34d ago
4
✓ held half
7 days
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
No region tag appears for [JP/Tokyo] Solo/Duo/Trio, but the name suggests Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 160.251.250.21:28015.
How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it up?
The server is up: [JP/Tokyo] Solo/Duo/Trio is online now. According to its reported uptime, the last restart was about 5 days 19 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Is [JP/Tokyo] Solo/Duo/Trio smooth to play on?
It averaged 73 server fps over the last 48 hours, with a low of 53. At its peak, it held 78,837 entities, including buildings, deployables and all else in the world. Up to 4,282 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is [JP/Tokyo] Solo/Duo/Trio on?
You will find [JP/Tokyo] Solo/Duo/Trio on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [JP/Tokyo] Solo/Duo/Trio reset?
[JP/Tokyo] Solo/Duo/Trio wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 6 days 10 hours.
What should you expect from wipe day on [JP/Tokyo] Solo/Duo/Trio?
Across its recent wipes, the busiest moments averaged 5 players. 32 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Player numbers
Where does [JP/Tokyo] Solo/Duo/Trio place in the wider field of Rust servers?
Over the last seven days, [JP/Tokyo] Solo/Duo/Trio has #1,559 for player hours, in the top 7% of all ranked servers.
What does the population on [JP/Tokyo] Solo/Duo/Trio look like?
[JP/Tokyo] Solo/Duo/Trio is showing 1 players right now, with 100 slots in total. Averaging 4 players over seven days, it peaked at 11. The highest average in the last 48 hours came at 15:00 UTC, with 9 players.
Tags and filters
How should you read the tags on [JP/Tokyo] Solo/Duo/Trio?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags [JP/Tokyo] Solo/Duo/Trio publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [JP/Tokyo] Solo/Duo/Trio?
These Rust Server Score lists count [JP/Tokyo] Solo/Duo/Trio among them: Best community servers, graded. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is [JP/Tokyo] Solo/Duo/Trio set up, and what rules does it keep?
Nothing in the name of [JP/Tokyo] Solo/Duo/Trio states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on [JP/Tokyo] Solo/Duo/Trio?
A procedural map of size 3,500 and seed 17761776, generated by the game, is what [JP/Tokyo] Solo/Duo/Trio 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] Solo/Duo/Trio?
To connect, start Rust, press F1, and type client.connect 160.251.250.21:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/QjJSb4U6T.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
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 good term. Strongest in performance (A+); population is the one to work on (F).