Working its way up from the back of the class: #15,478 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
51/ 100
D
Moving up: up 372 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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 typical TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 192.255.237.203:28023.
How reliable is typical TEST, and is it up?
You cannot join now: typical TEST is offline, last seen 39 days 13 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 September 2026, Rust Server Score saw it for the first time.
What Rust version is typical TEST on?
The server typical TEST is on Rust network protocol 2633 and build 164530 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does typical TEST reset?
There are too few wipes on record for typical TEST 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. 40 days 13 hours have passed since this world was made.
Population
What position does typical TEST hold in the rankings?
Over the last seven days, typical TEST has #15,478 for player hours, in the top 70% of all ranked servers.
Is typical TEST a busy server?
It has been 39 days 13 hours since typical TEST was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on typical TEST?
The game's browser takes its cue from the tags typical TEST has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 typical TEST?
Rust Server Score lists that include typical TEST: 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.
Map and rules
Which rules does typical TEST enforce, and what are its settings?
You will find no gather rate in the name of typical TEST. The group limit stays at the game's default of 8 players. It runs survival, 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. The server runs Valve's anti-cheat, VAC.
typical TEST runs which map?
The game generates the procedural map on typical TEST at size 1,000 with seed 6738. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to typical TEST?
Enter client.connect 192.255.237.203:28023 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 players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 momentum (D); standing is the one to work on (F).