Working its way up from the back of the class: #13,064 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
24/ 100
F
Lost ground: down 6,854 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
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 59% 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.7 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Tue 20 OctMon 19 Oct
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
Tue 20 Oct, 13:02 UTC7d ago
1
–
running
1
Mon 19 Oct, 19:31 UTC8d ago
1
–
0.7 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
No region is published for Test player. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 191.95.166.236:28015 is the address to use.
How reliable is Test player, and is it up?
At this moment, Test player is offline; the last time it was seen was 7 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 October 2026, Rust Server Score saw it for the first time.
What Rust version is Test player on?
The server Test player is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Test player wipe, and how often?
The record holds too few of Test player'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. The world it runs now was created 7 days 22 hours.
What happens on Test player when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Test player sit among Rust servers?
Over the last seven days, Test player has #13,064 for player hours, in the top 59% of all ranked servers.
How many players does Test player usually have?
It has been 7 days 17 hours since Test player was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Test player?
You'll see Test player tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. 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 Test player?
Rust Server Score lists that include Test player: 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 2 weeks.
Server rules
Which rules does Test player enforce, and what are its settings?
The name of Test player gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in 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.
Test player runs which map?
A procedural map, generated by the game, is what Test player runs.
Getting in
How should you connect to Test player?
Enter client.connect 191.95.166.236: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 asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
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 (F); momentum is the one to work on (F).