On the class lists: F (38), with population over 48 hours and no performance mark.
Players now1/ 425% full
7-day average1peak 1
Rank#5,569top 25%
Last wipe4d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
18/ 100
F
A quiet classroom so far: 1 of 4 on average. Plenty of space to grow.
Standingrank on player hours
75/ 100
B
Holds a respectable place: #5,569 on player hours.
Uptimehours on the list, last 48
17/ 100
F
Attendance needs work: on the list only 8 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); uptime 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
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 25% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll find no region listed by rustctl-localtest. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 217.94.246.164:28015.
How reliable is rustctl-localtest, and is it up?
You can join now: rustctl-localtest is online. It was up 39% of the time over the last 4 full days, 37 of 96 hours. It was first seen by Rust Server Score on 24 October 2026.
What Rust version is rustctl-localtest on?
Rust network protocol 2635 and build 168909 on Windows is what rustctl-localtest runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does rustctl-localtest wipe, and how often?
The record holds too few of rustctl-localtest'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. 4 days 6 hours have passed since this world was made.
Player numbers
Where does rustctl-localtest place in the wider field of Rust servers?
Over the last seven days, rustctl-localtest has #5,569 for player hours, in the top 25% of all ranked servers.
What does the population on rustctl-localtest look like?
Right now, 1 players are on rustctl-localtest, which has 4 slots. Averaging 1 players over seven days, it peaked at 1. The highest average in the last 48 hours came at 23:00 UTC, with 1 players.
Tags and filters
What do rustctl-localtest's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): 4 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags rustctl-localtest 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.
Where does rustctl-localtest appear in the Rust Server Score lists and filters?
Rust Server Score lists that include rustctl-localtest: 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 rustctl-localtest set up, and what rules does it keep?
The name of rustctl-localtest gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is not enabled.
Which map is in play on rustctl-localtest?
A procedural map, generated by the game, is what rustctl-localtest runs.
How to join
How do you get onto rustctl-localtest?
Enter client.connect 217.94.246.164:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max players4 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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); uptime is the one to work on (F).