On the class lists: C+ (67), with population over 48 hours and no performance mark.
Players now0/ 320% full
7-day average1peak 2
Rank#3,755top 17%
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 1 of 32 on average. Plenty of space to grow.
Standingrank on player hours
83/ 100
B+
Holds a respectable place: #3,755 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
48/ 100
D
Needs to work on its frame rate: 29 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
56/ 100
C−
Moving up: up 449 places this week.
A fair term, with more to come.
Strongest in wipe hold (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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 17% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
······W
···FW··
·····W·
····W··
···WW··
·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 gap5.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Fri 23 OctThu 22 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 15:28 UTC1d ago
–
–
running
0
Fri 23 Oct, 14:41 UTC5d ago
2
✓ held half
4 days
0
Thu 22 Oct, 18:15 UTC6d ago
2
–
0.9 days
0
Fri 16 Oct, 15:30 UTC12d ago
2
✓ held half
6.1 days
1
Sat 10 Oct, 10:38 UTC18d ago
2
✓ held half
6.2 days
0
Fri 2 Oct, 08:30 UTC26d ago
2
✓ held half
8.1 days
1
Thu 1 Oct, 18:14 UTCFW27d ago
2
–
0.6 days
1
Sun 27 Sep, 11:04 UTC31d ago
2
✓ held half
4.3 days
2
Sat 19 Sep, 11:14 UTC39d ago
2
✓ held half
8 days
1
Fri 18 Sep, 17:40 UTC40d ago
2
–
0.7 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
BlaKam Testserver leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 85.14.198.168:28015.
Is BlaKam Testserver up, and how steady is its uptime?
Right now, BlaKam Testserver is online. About 6 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 166 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does BlaKam Testserver perform well?
The average over the last 48 hours was 29 server fps, and it never went below 4. At its peak, it held 150,304 entities, including buildings, deployables and all else in the world. At its highest, it used 4,232 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is BlaKam Testserver on?
You will find BlaKam Testserver on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does BlaKam Testserver wipe its map?
There is no next wipe to predict on BlaKam Testserver, as it wipes at irregular times. 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 5 days 13 hours.
What happens on BlaKam Testserver when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Population
What position does BlaKam Testserver hold in the rankings?
In the top 17% of all ranked servers, BlaKam Testserver sits at #3,755 for player hours over the last seven days.
How many players does BlaKam Testserver usually have?
With 32 slots available, BlaKam Testserver currently has 0 players. The seven-day average is 1 players, with a peak of 2. The highest average in the last 48 hours came at 17:00 UTC, with 1 players.
Lists and filters
How should you read the tags on BlaKam Testserver?
gmvanilla (Game mode): Survival, vanilla style; mp32 (Max players): 32 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags BlaKam Testserver publishes, and the game's server browser reads them. 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 BlaKam Testserver appear in the Rust Server Score lists and filters?
Rust Server Score lists that include BlaKam Testserver: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Server rules
How is BlaKam Testserver set up, and what rules does it keep?
Nothing in the name of BlaKam Testserver states a gather rate. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map BlaKam Testserver uses?
A procedural map of size 5,000 and seed 1972576941, generated by the game, is what BlaKam Testserver runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to BlaKam Testserver?
Enter client.connect 85.14.198.168: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 asmp32,ptrak,$r?,v2635,^p,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp32
Max players32 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 fair term, with more to come. Strongest in wipe hold (A+); population is the one to work on (F).