Working its way up from the back of the class: #14,947 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
34/ 100
F
Lost ground: down 4,912 places this week. A strong wipe could turn it round.
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.
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.
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
·W·W···
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap13 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Thu 22 OctTue 20 OctSat 26 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
Thu 22 Oct, 17:13 UTC6d ago
1
–
running
1
Tue 20 Oct, 02:39 UTC8d ago
2
–
2.6 days
0
Sat 26 Sep, 17:54 UTC32d ago
1
–
23.4 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
In what location does (Classy) Rust Testing 1 sit?
No region is published for (Classy) Rust Testing 1. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 94.130.167.253:28014.
How reliable is (Classy) Rust Testing 1, and is it up?
You cannot join now: (Classy) Rust Testing 1 is offline, last seen 5 days 23 hours ago. It was up 5 of 168 hours over the last 7 full days, which is 3% of the time. The first sighting by Rust Server Score was on 25 September 2026.
On what Rust version does (Classy) Rust Testing 1 sit?
Rust network protocol 2634 and build 167781 on Linux is what (Classy) Rust Testing 1 runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does (Classy) Rust Testing 1 reset?
There is no next wipe to predict on (Classy) Rust Testing 1, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 6 days 3 hours.
What should you expect from wipe day on (Classy) Rust Testing 1?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does (Classy) Rust Testing 1 sit among Rust servers?
In the top 67% of all ranked servers, (Classy) Rust Testing 1 sits at #14,947 for player hours over the last seven days.
What does the population on (Classy) Rust Testing 1 look like?
The last sighting of (Classy) Rust Testing 1 was 5 days 23 hours ago, and it is offline right now. The seven-day average is 0 players, with a peak of 1.
Lists and filters
How should you read the tags on (Classy) Rust Testing 1?
The game's browser takes its cue from the tags (Classy) Rust Testing 1 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp0 (Max players): Its slot count is 0; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does (Classy) Rust Testing 1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count (Classy) Rust Testing 1 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Server rules
How is (Classy) Rust Testing 1 set up, and what rules does it keep?
You will find no gather rate in the name of (Classy) Rust Testing 1. 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. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on (Classy) Rust Testing 1?
A procedural map of size 2,048 and seed 1337, generated by the game, is what (Classy) Rust Testing 1 runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Connecting
How do you get onto (Classy) Rust Testing 1?
Enter client.connect 94.130.167.253:28014 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 asmp0,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp0
Max playersIts slot count is 0.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^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.