On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,318top 69%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 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,318 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
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 6,457 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (F); 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
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 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W··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 gap3.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held33%else halves by day 4
The first 48 hours of its last wipes
Sat 17 OctMon 5 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 00:30 UTC12d ago
2
–
running
0
Mon 5 Oct, 18:31 UTC23d ago
3
halved by day 7
11.2 days
2
Thu 1 Oct, 15:42 UTC27d ago
1
✓ held half
4.1 days
0
Thu 1 Oct, 06:00 UTC28d ago
2
–
0.4 days
0
Mon 28 Sep, 17:57 UTC30d ago
2
halved by day 1
2.5 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
No region is published for Stillwater Testing. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 168.100.162.13:29015 is the address to use.
Is Stillwater Testing up, and how steady is its uptime?
You cannot join now: Stillwater Testing is offline, last seen 4 days 14 hours ago. It was up 71 of 168 hours over the last 7 full days, which is 42% of the time. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is Stillwater Testing running?
Rust network protocol 2634 and build 167781 on Linux is what Stillwater Testing runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Stillwater Testing wipe, and how often?
No next wipe can be predicted for Stillwater Testing, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 12 days 11 hours have passed since this world was made.
What happens on Stillwater Testing when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 2 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Player count
What position does Stillwater Testing hold in the rankings?
In the top 69% of all ranked servers, Stillwater Testing sits at #15,318 for player hours over the last seven days.
Is Stillwater Testing a busy server?
Stillwater Testing is offline at the moment; the last time it was seen was 4 days 14 hours ago. A seven-day average of 0 players applies here.
Lists and filters
How should you read the tags on Stillwater Testing?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts30 (Group limit): Teams cap out at 30; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags Stillwater Testing 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 operates Stillwater Testing?
A stillwatershores.org hostname is published by Stillwater Testing, and 1 other server we track does the same, which points to one operator running them.
Which lists and filters on Rust Server Score show Stillwater Testing?
Rust Server Score lists that include Stillwater Testing: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does Stillwater Testing enforce, and what are its settings?
Nothing in the name of Stillwater Testing states a gather rate. A group here can reach 30 players. survival is the mode here, gather and build and raid: the standard game. 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 Carbon. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Stillwater Testing uses?
Stillwater Testing runs a game-generated procedural map at size 5,000, seed 1383972055. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
How to join
What is the way to join Stillwater Testing?
To connect, start Rust, press F1, and type client.connect 168.100.162.13:29015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,^z,^y,^v,gmrust,cs167781,ts30
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts30
Group limitTeams cap out at 30.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under 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. Strongest in wipe hold (F); population is the one to work on (F).