On the class lists: B− (70), with population over 48 hours and no performance mark.
Players now1/ ?
7-day average0peak 1
Rank#5,209top 23%
Last wipe11h agobiweekly schedule
Next wipe6d 22hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
77/ 100
B
Holds a respectable place: #5,209 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 250 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
76/ 100
B
Climbing fast: up 2,703 places this week.
A good term.
Strongest in performance (A+); wipes are 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 23% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WW·F···
·····W·
·······
·······
···W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h.
The force wipe · high confidence
usual gap5.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held33%else halves by day 1
Coming wipes
6d 22hThu 5 Nov, 19:00 UTCFW
13d 12hThu 12 Nov, 08:53 UTC
27d 12hThu 26 Nov, 08:53 UTC
34d 22hThu 3 Dec, 19:00 UTCFW
41d 12hThu 10 Dec, 08:53 UTC
The first 48 hours of its last wipes
Sat 10 OctThu 1 OctTue 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
Thu 29 Oct, 08:53 UTC11h ago
–
–
running
0
Sat 10 Oct, 19:22 UTC19d ago
1
–
–
1
Thu 1 Oct, 18:23 UTCFW28d ago
1
halved by day 1
9 days
0
Tue 29 Sep, 17:59 UTC30d ago
1
✓ held half
2 days
0
Mon 28 Sep, 19:01 UTC31d ago
1
–
1 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
TESTTTTT leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 5.182.207.231:11000 is the address to use.
How reliable is TESTTTTT, and is it up?
The server is up: TESTTTTT is online now. According to its reported uptime, the last restart was about 9 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Is TESTTTTT smooth to play on?
It averaged 300 server fps over the last 48 hours, with a low of 184. At its peak, it held 370,382 entities, including buildings, deployables and all else in the world. Memory use reached up to 9,874 MB. Players feel lag when fps drops and entities pile up.
What Rust version is TESTTTTT on?
You will find TESTTTTT on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does TESTTTTT wipe, and how often?
The prediction follows its tag, because too few of TESTTTTT's wipes are on record to confirm the schedule. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 11 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
What happens on TESTTTTT when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 33% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player count
What position does TESTTTTT hold in the rankings?
Over the last seven days, TESTTTTT has #5,209 for player hours, in the top 23% of all ranked servers.
What does the population on TESTTTTT look like?
The current population of TESTTTTT is 1 players. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 10:00 UTC, with an average of 1 players.
Tags
What is meant by the tags on TESTTTTT?
You'll see TESTTTTT tagged with gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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; ^b (Biweekly): A wipe happens once a fortnight; ^h (Hardcore): Fewer helpers and harsher survival: that is Facepunch's hardcore mode; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded 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 TESTTTTT appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TESTTTTT among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, Hardcore ^h, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Map and rules
How is TESTTTTT set up, and what rules does it keep?
You will find no gather rate in the name of TESTTTTT. The default of 8 players applies as the group cap. hardcore is the mode here, Facepunch's most punishing mode. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on TESTTTTT?
A procedural map of size 4,500 and seed 2234235, generated by the game, is what TESTTTTT runs. 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 should you connect to TESTTTTT?
To connect, start Rust, press F1, and type client.connect 5.182.207.231:11000. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://rust-z.gamestores.app/.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,^b,^h,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max players0 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
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
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^h
HardcoreFewer helpers and harsher survival: that is Facepunch's hardcore mode.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 good term. Strongest in performance (A+); wipes are the one to work on (F).