On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 90% full
7-day average0peak –
Rank#15,409top 69% · #2591 in EU
Last wipe23d agoweekly schedule
Next wipe4d 1hSun 1 Nov, 02:15 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 9 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,409 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 179 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, top 89% in EU, and #626 of the quad servers (top 76%). 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
Next wipe Sunday 1 November, 02:15 UTC, in 4d 1h.
Weekly: 7 days after its last 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
The EU tag on Testing server puts it in Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 37.187.28.4:28023.
Is Testing server up, and how steady is its uptime?
Right now, Testing server is online. According to its reported uptime, the last restart was about 2 days 3 hours ago. It was up 144 of 168 hours over the last 7 full days, which is 86% of the time. The first sighting by Rust Server Score was on 4 October 2026.
Is Testing server smooth to play on?
The average over the last 48 hours was 30 server fps, and it never went below 28. Buildings, deployables and everything else in the world added up to as many as 3,024 entities. At its highest, it used 1,123 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Testing server sit?
Rust network protocol 2635 and build 168909 on Linux is what Testing server runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Testing server wipe its map?
The estimate for Testing server's next wipe comes from weekly: 7 days after its last wipe. Sunday 1 November at 02:15 UTC is the date set for its next wipe. It has been running its current world for 23 days 22 hours. Its tags state that it wipes weekly.
Population
What position does Testing server hold in the rankings?
In Europe, Testing server is #2,591, and overall it is #15,409 on player hours over the last seven days, in the top 69% of all ranked servers. It comes #626 among servers in the quad group.
Is Testing server a busy server?
Testing server is showing 0 players right now, with 9 slots in total. A seven-day average of 0 players applies here.
Tags
How should you read the tags on Testing server?
gmrust (Game mode): Rust survival, played by the standard rules; mp9 (Max players): Its slot count is 9; ts4 (Group limit): Teams cap out at 4; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon; EU (Europe): The server browser lists it under Europe are the tags Testing server publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Who is behind Testing server?
Among all the servers we track, only Testing server publishes this slimi.lt hostname.
Where does Testing server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Testing server: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Weekly.
Rules and settings
What settings and rules apply on Testing server?
Nothing in the name of Testing server states a gather rate. The cap on group size is 4 players (quad). You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Testing server uses?
Testing server runs a game-generated procedural map at size 1,000, seed 1234. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join Testing server?
Enter client.connect 37.187.28.4:28023 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://basemates.net.
Server tags
what each one means
Published asmp9,ptrak,$r?,v2635,^z,^y,^w,EU,gmrust,cs168909,ts4
Game
gmrust
Game modeRust survival, played by the standard rules.
mp9
Max playersIts slot count is 9.
ts4
Group limitTeams cap out at 4.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
Region
EU
EuropeThe server browser lists it under Europe.
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 uptime (A+); population is the one to work on (F).