Rust Player Count
60,559 playing now

Offline168.100.162.13:29015checked 1d ago

Stillwater Testing

vanillamoddedoxide
Players now 0/ 40 0% full
7-day average 0 peak 3
Rank #4,930 top 22%
Last wipe 9d ago no schedule published
Next wipe – no rhythm it keeps

Players

AveragePeak
00.250.50.75113:0016:0019:0021:0000:0003:00

Hourly average and peak, UTC.

Server performance

02040608013:0016:0019:0021:0000:0003:00

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
15k10k15k20k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

Top 22% of all ranked servers. Ranked on player hours over the last seven days.

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 gap 2.5 days between real wipes
On rhythm 33% of its recent wipes
Wipe-day peak 2 players, last three wipes
Crowd held 50% else halves by day 1

The first 48 hours of its last wipes

Mon 5 OctThu 1 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 43 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 18:31 UTC9d ago 3 – running 2
Thu 1 Oct, 15:42 UTC13d ago 1 held half 4.1 days 0
Thu 1 Oct, 06:00 UTC14d ago 2 – 0.4 days 0
Mon 28 Sep, 17:57 UTC16d 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

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimitno group limit · 128 on average 139/ 300
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average 0/ 225
МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average 88/ 100
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average 23/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 74 on average 13/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 71 on average 37/ 700

Quick answers

from the figures on this page

Settings and map

Which rules govern Stillwater Testing?

A gather rate is absent from the name of Stillwater Testing. Up to 8 players per group, which is the game's default. survival is the game mode, gather, build, raid: the standard game. PvP and raiding are enabled. The server browser lists it under Modded, because plugins or settings alter the game. Plugins: Oxide. Its own label is vanilla: the standard Facepunch version, without modifications to rates, kits or rules. Anti-cheat VAC from Valve is on.

Which map is running on Stillwater Testing?

The game generates a procedural map of size 5,000 with seed 1383972055 for Stillwater Testing. You can see it on RustMaps from this page, because the same size and seed give the same map. You can see the map name here: Custom Map.

Server tags

Where can Stillwater Testing be found in Rust Player Count lists and filters?

These Rust Player Count lists include Stillwater Testing: Modded Rust servers. You can find it on the server list using these filters: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What information do the tags on Stillwater Testing convey?

For the game's server browser, Stillwater Testing publishes: gmrust (Game mode): The usual Rust survival experience; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): Joining requires the same protocol: 2634; cs166652 (Build): It runs on game build 166652; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): The region code field is empty; ^v (Vanilla): The standard Facepunch version, without modifications to rates, kits or rules; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded category: plugins or configuration change gameplay. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.

Player numbers

How full is Stillwater Testing?

The server Stillwater Testing is offline at present, with its last appearance 32 hours ago. The average player count for the last seven days is 0, and the highest point was 3. The busiest time in the last 48 hours was 17:00 UTC, with an average of 1 players.

How does Stillwater Testing compare in server rankings?

For player hours in the last seven days, Stillwater Testing ranks #4,930 and is in the top 22% of all ranked servers.

About the server

What is the online status and reliability of Stillwater Testing?

Last seen 32 hours ago, Stillwater Testing is offline right now. The uptime it gives suggests it restarted about 8 days 8 hours ago. It was up 88% of the time over the last 7 full days, 148 of 168 hours. Its first appearance in Rust Player Count was on 13 September 2026.

What Rust version is used on Stillwater Testing?

Linux hosts Stillwater Testing, which runs Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam updates it for you.

What region does Stillwater Testing serve?

A region is not published by Stillwater Testing. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. You can reach it at 168.100.162.13:29015.

How well does Stillwater Testing perform?

The server ran at an average of 59 fps over the last 48 hours, never falling below 55. The maximum number of entities it carried was 148,381, which includes buildings, deployables and everything else. At its highest, it used 5,842 MB of memory. Lag, as players experience it, is caused by low fps and increasing entities.

Wipe information

What changes on Stillwater Testing on wipe day?

The average busiest point in recent wipes reached 2 players. The latest wipe saw its biggest crowd 43 hours in. Half that peak was maintained until the next wipe in 50% of recent wipes. If not, the crowd went below half by day 1.

What wipe pattern does Stillwater Testing follow?

No next wipe can be predicted for Stillwater Testing, as it wipes at irregular times. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. It has been running its current world for 9 days 18 hours.

Join the server

What steps are needed to join Stillwater Testing?

Joining is done by opening the console (F1) and running client.connect 168.100.162.13:29015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,^v,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The usual Rust survival experience.
mp40
Max players Capacity: 40 slots.
ts8
Group limit This uses the default team cap: 8 players.
v2634
Protocol Joining requires the same protocol: 2634.
cs166652
Build It runs on game build 166652.
ptrak
Networking RakNet is the game's usual network protocol, and this server uses it.
$r?
Region code The region code field is empty.

Difficulty

^v
Vanilla The standard Facepunch version, without modifications to rates, kits or rules.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded The Modded category: plugins or configuration change gameplay.

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.