Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·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.
usual gap1.9 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sat 19 SepThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 19 Sep, 05:20 UTC39d ago
0
–
running
0
Thu 17 Sep, 07:02 UTC41d ago
0
–
1.9 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
typical TEST leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 9.244.16.170:28015.
How reliable is typical TEST, and is it up?
The server is down: typical TEST is offline now, with the last sighting 39 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 16 September 2026.
Which Rust version is typical TEST running?
You will find typical TEST on Rust network protocol 2633 and build 164530, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does typical TEST wipe its map?
The record holds too few of typical TEST'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 39 days 10 hours.
What happens on typical TEST when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does typical TEST sit among Rust servers?
In the top – of all ranked servers, typical TEST sits at #15,413 for player hours over the last seven days.
How many players does typical TEST usually have?
The last sighting of typical TEST was 39 days ago, and it is offline right now.
Tags and filters
What do typical TEST's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags typical TEST publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature typical TEST?
Rust Server Score lists that include typical TEST: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on typical TEST?
You will find no gather rate in the name of typical TEST. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. 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.
Can you tell me which map typical TEST uses?
The game generates a procedural map for typical TEST.
Getting in
How should you connect to typical TEST?
Enter client.connect 9.244.16.170: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 asmp100,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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.
Not enough figures yet to write a report. Check back after a few days on the list.