On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average2peak 10
Rank#4,069top 18%
Last wipe12d agono schedule published
Next wipe1d 11hFri 30 Oct, 08:38 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 2 of 150 on average. Plenty of space to grow.
Standingrank on player hours
82/ 100
B+
Holds a respectable place: #4,069 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
11/ 100
F
Lost ground: down 3,197 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (B+); 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
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.
AveragePeakWipe
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 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 18% of all ranked servers, and #298 of the trio servers (top 48%). Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
····W··
····W··
····W··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Friday 30 October, 08:38 UTC, in 1d 11h.
Every 7 days · medium confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak49players, last three wipes
crowd held0%else halves by day 3.5
Coming wipes
1d 11hFri 30 Oct, 08:38 UTC
7d 22hThu 5 Nov, 19:00 UTCFW
8d 11hFri 6 Nov, 08:30 UTC
15d 11hFri 13 Nov, 08:23 UTC
22d 11hFri 20 Nov, 08:16 UTC
29d 11hFri 27 Nov, 08:09 UTC
35d 22hThu 3 Dec, 19:00 UTCFW
36d 11hFri 4 Dec, 08:02 UTC
The first 48 hours of its last wipes
Fri 16 OctFri 9 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 48, 30 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 08:52 UTC12d ago
48
–
running
1
Fri 9 Oct, 08:59 UTC19d ago
45
halved by day 4
7 days
3
Fri 2 Oct, 09:06 UTC26d ago
54
halved by day 4
7 days
0
Fri 25 Sep, 06:39 UTC33d ago
85
halved by day 3
7.1 days
2
Fri 18 Sep, 07:43 UTC40d ago
99
halved by day 2
7 days
2
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/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 based in?
The name of JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 157.85.88.181:28015.
How dependable is JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16, and is it online at the moment?
At this moment, JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 is offline; the last time it was seen was 5 days 10 hours ago. It was up 59 of 168 hours over the last 7 full days, which is 35% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 sit?
Rust network protocol 2634 and build 167781 on Linux is what JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 wipe, and how often?
Recent wipes on JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 have come about every 7 days. Expect the next wipe on Friday 30 October at 08:38 UTC. It has been running its current world for 12 days 12 hours.
What should you expect from wipe day on JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16?
Recent wipes have peaked at 49 players on average. The crowd on the latest wipe was largest 30 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 3.5 in the wipes where it did not hold.
Player numbers
Where does JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 place in the wider field of Rust servers?
In the top 18% of all ranked servers, JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 sits at #4,069 for player hours over the last seven days. It comes #298 among servers in the trio group.
Is JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 a busy server?
The last sighting of JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 was 5 days 10 hours ago, and it is offline right now. The seven-day average is 2 players, with a peak of 10.
Tags and filters
What do JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16's tags stand for?
The game's browser takes its cue from the tags JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): The server holds 150 slots; ts3 (Group limit): Teams cap out at 3; 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): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod). 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-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16?
These Rust Server Score lists count JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 among them: Best community servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Trio; Last wipe: In the last 2 weeks.
Rules and settings
How is JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 set up, and what rules does it keep?
You will find no gather rate in the name of JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16. The cap on group size is 3 players (trio). It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 runs which map?
JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16 runs a game-generated procedural map at size 3,500, seed 1830751865. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto JP/Tokyo-RustSamurai Solo/Duo/Trio 初心者/社会人wip10/16?
To connect, start Rust, press F1, and type client.connect 157.85.88.181:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/UP8yKH2vrs.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2634,gmrust,cs167781,ts3,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp150
Max playersThe server holds 150 slots.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 term to build on. Strongest in standing (B+); wipes are the one to work on (F).