A quiet classroom so far: 1 of 500 on average. Plenty of space to grow.
Standingrank on player hours
71/ 100
B−
Holds a respectable place: #6,438 on player hours.
Uptimehours on the list, last 48
46/ 100
D
Attendance needs work: on the list only 22 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
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
83/ 100
B+
Climbing fast: up 4,227 places this week.
A fair term, with more to come.
Strongest in wipe hold (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.
AveragePeakWipe
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
······W
WW·····
···WW··
·······
··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 gap0.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 02:24 UTC1d ago
–
–
running
1
Fri 16 Oct, 09:33 UTC12d ago
1
–
11.7 days
1
Thu 15 Oct, 20:39 UTC13d ago
1
–
0.5 days
1
Thu 15 Oct, 11:41 UTC13d ago
1
–
0.4 days
1
Tue 6 Oct, 14:19 UTC22d ago
2
✓ held half
8.9 days
1
Mon 5 Oct, 08:09 UTC23d ago
2
–
1.3 days
1
Sun 4 Oct, 22:55 UTC24d ago
2
–
0.4 days
0
Sun 4 Oct, 16:08 UTC24d ago
1
–
0.3 days
0
Tue 22 Sep, 09:48 UTC36d ago
2
halved by day 1
12.3 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
Where in the world is 4500 JP/CHIBA PvE 10X NoBPWipe?
You won't find a region tag on 4500 JP/CHIBA PvE 10X NoBPWipe, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 59.139.138.172:28015.
Is 4500 JP/CHIBA PvE 10X NoBPWipe up, and how steady is its uptime?
You can join now: 4500 JP/CHIBA PvE 10X NoBPWipe is online. It was up 17 of 168 hours over the last 7 full days, which is 10% of the time. The first sighting by Rust Server Score was on 18 September 2026.
Which Rust version is 4500 JP/CHIBA PvE 10X NoBPWipe running?
Rust network protocol 2635 and build 168909 on Windows is what 4500 JP/CHIBA PvE 10X NoBPWipe runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does 4500 JP/CHIBA PvE 10X NoBPWipe wipe its map?
No next wipe can be predicted for 4500 JP/CHIBA PvE 10X NoBPWipe, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 26 hours have passed since this world was made.
What happens on 4500 JP/CHIBA PvE 10X NoBPWipe when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 100% of its recent wipes.
Population
What position does 4500 JP/CHIBA PvE 10X NoBPWipe hold in the rankings?
Over the last seven days, 4500 JP/CHIBA PvE 10X NoBPWipe has #6,438 for player hours, in the top 29% of all ranked servers.
Is 4500 JP/CHIBA PvE 10X NoBPWipe a busy server?
With 500 slots available, 4500 JP/CHIBA PvE 10X NoBPWipe currently has 1 players. It peaked at 2 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 09:00 UTC, with 2 players.
Tags and filters
What do 4500 JP/CHIBA PvE 10X NoBPWipe's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): Its slot count is 500; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags 4500 JP/CHIBA PvE 10X NoBPWipe publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show 4500 JP/CHIBA PvE 10X NoBPWipe?
Rust Server Score lists that include 4500 JP/CHIBA PvE 10X NoBPWipe: 10x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days; Gather rate: 10x.
Rules and settings
How is 4500 JP/CHIBA PvE 10X NoBPWipe set up, and what rules does it keep?
The name of 4500 JP/CHIBA PvE 10X NoBPWipe points to a 10x gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server does not run VAC, Valve's anti-cheat.
Which map is in play on 4500 JP/CHIBA PvE 10X NoBPWipe?
The game generates a procedural map for 4500 JP/CHIBA PvE 10X NoBPWipe.
Connecting
How should you connect to 4500 JP/CHIBA PvE 10X NoBPWipe?
To connect, start Rust, press F1, and type client.connect 59.139.138.172:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max playersIts slot count is 500.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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 wipe hold (A+); population is the one to work on (F).