Working its way up from the back of the class: #16,964 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
26/ 100
F
Lost ground: down 8,156 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 21 Sep, 23:30 UTC37d ago
2
–
running
1
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
Josh's Rust Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 173.250.132.166:28015.
How reliable is Josh's Rust Server, and is it up?
You cannot join now: Josh's Rust Server is offline, last seen 31 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Josh's Rust Server sit?
You will find Josh's Rust Server on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Josh's Rust Server wipe its map?
The record holds too few of Josh's Rust Server's wipes to tell 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 37 days 12 hours.
What happens on Josh's Rust Server when wipe day arrives?
The average peak on its recent wipes was 2 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Josh's Rust Server place in the wider field of Rust servers?
Over the last seven days, Josh's Rust Server has #16,964 for player hours, in the top 71% of all ranked servers.
How many players does Josh's Rust Server usually have?
Josh's Rust Server is offline at the moment; the last time it was seen was 31 days 22 hours ago.
Tags
What is meant by the tags on Josh's Rust Server?
gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): 5 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set are the tags Josh's Rust Server 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 Josh's Rust Server?
Rust Server Score lists that include Josh's Rust Server: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Josh's Rust Server?
Nothing in the name of Josh's Rust Server states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Josh's Rust Server uses?
A procedural map, generated by the game, is what Josh's Rust Server runs.
How to join
What is the way to join Josh's Rust Server?
To connect, start Rust, press F1, and type client.connect 173.250.132.166:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max players5 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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. Even marks across the subjects, from F to F.