A quiet classroom so far: 1 of 500 on average. Plenty of space to grow.
Standingrank on player hours
78/ 100
B
Holds a respectable place: #4,784 on player hours.
Uptimehours on the list, last 48
21/ 100
F
Attendance needs work: on the list only 10 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (B); 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
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 22% 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 peak1players, last three wipes
The first 48 hours of its last wipes
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
Sun 25 Oct, 07:10 UTC4d ago
1
–
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
Razolak's Local Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 103.225.230.17:28015 is the address to use.
How dependable is Razolak's Local Server, and is it online at the moment?
The server is down: Razolak's Local Server is offline now, with the last sighting 24 hours ago. It was up 40% of the time over the last 5 full days, 48 of 120 hours. On 23 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Razolak's Local Server sit?
Rust network protocol 2635 and build 168909 on Windows is what Razolak's Local Server runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Razolak's Local Server wipe, and how often?
There are too few wipes on record for Razolak's Local Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 4 days 4 hours have passed since this world was made.
What should you expect from wipe day on Razolak's Local Server?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does Razolak's Local Server place in the wider field of Rust servers?
In the top 22% of all ranked servers, Razolak's Local Server sits at #4,784 for player hours over the last seven days.
Is Razolak's Local Server a busy server?
The last sighting of Razolak's Local Server was 24 hours ago, and it is offline right now. The seven-day average is 1 players, with a peak of 1. The busiest time in the last 48 hours was 04:00 UTC, with an average of 1 players.
Tags
How should you read the tags on Razolak's Local Server?
The game's browser takes its cue from the tags Razolak's Local Server has set: gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): The server holds 500 slots; 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): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Razolak's Local Server?
Rust Server Score lists that include Razolak's Local Server: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is Razolak's Local Server set up, and what rules does it keep?
Nothing in the name of Razolak's Local Server states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Razolak's Local Server runs which map?
A procedural map, generated by the game, is what Razolak's Local Server runs.
Getting in
How should you connect to Razolak's Local Server?
To connect, start Rust, press F1, and type client.connect 103.225.230.17: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
Game
gmrust
Game modeSurvival in the standard Rust style.
mp500
Max playersThe server holds 500 slots.
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
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. Strongest in standing (B); population is the one to work on (F).