Working its way up from the back of the class: #15,705 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
35/ 100
F
Slipped a little: down 4,803 places this week. Nothing a good wipe can't fix.
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.
AveragePeak
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 66% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
·······
·······
·······
···
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 gap0.8 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 30 SepTue 29 Sep
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
Wed 30 Sep, 12:18 UTC28d ago
1
–
running
1
Tue 29 Sep, 16:58 UTC29d ago
1
–
0.8 days
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
You'll find no region listed by TEST TEST TEST. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 87.126.166.148:28025.
How reliable is TEST TEST TEST, and is it up?
You cannot join now: TEST TEST TEST is offline, last seen 28 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 24 September 2026, Rust Server Score saw it for the first time.
Which Rust version is TEST TEST TEST running?
You will find TEST TEST TEST on Rust network protocol 2633 and build 165217, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does TEST TEST TEST reset?
TEST TEST TEST has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 28 days 8 hours have passed since this world was made.
What should you expect from wipe day on TEST TEST TEST?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
What position does TEST TEST TEST hold in the rankings?
In the top 66% of all ranked servers, TEST TEST TEST sits at #15,705 for player hours over the last seven days.
How many players does TEST TEST TEST usually have?
The last sighting of TEST TEST TEST was 28 days 6 hours ago, and it is offline right now.
Lists and filters
What do TEST TEST TEST's tags stand for?
You'll see TEST TEST TEST tagged with gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): Its slot count is 500; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does TEST TEST TEST appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TEST TEST TEST among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Carbon ^y; Group limit: 5 or more.
Map and rules
Which rules does TEST TEST TEST enforce, and what are its settings?
Nothing in the name of TEST TEST TEST states a gather rate. The default of 8 players applies as the group cap. You get survival here, 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. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
TEST TEST TEST runs which map?
The game generates the procedural map on TEST TEST TEST at size 4,096 with seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Getting in
How do you get onto TEST TEST TEST?
Enter client.connect 87.126.166.148:28025 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 asmp500,ptrak,$r?,v2633,gmrust,cs165217,ts8,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp500
Max playersIts slot count is 500.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^y
CarbonThe plugin framework in use is Carbon.
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.