TST12338=
Testing Dumb Things
Online NA 66.51.96.89:28000 checked 9m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 55% of all ranked servers, top 73% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 20h.
The force wipe · high confidence
Coming wipes
- 6d 20hThu 5 Nov, 19:00 UTCFW
- 34d 20hThu 3 Dec, 19:00 UTCFW
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 21:44 UTC1d ago | – | – | running | 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
The same kind of game, then region, group limit, rate and wipes.
-
01MODPlayers 16/175
-
02MODPlayers 4/90
-
03MODPlayers 7/1000
-
04MODPlayers 3/15
-
05MODPlayers 2/50
-
06MODPlayers 1/50
Quick answers
From the figures on this page.
Filters
Where does Testing Dumb Things appear in Rust Tracker lists and filters?
These Rust Tracker lists carry Testing Dumb Things: Modded servers, tracked live and North America: live server tracking. On the server list, these filters bring it up: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
How should you read the tags on Testing Dumb Things?
Listed for the server browser to read, Testing Dumb Things publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Follows Facepunch's force wipe: one wipe per month; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; NA (North America): Server browser: listed under North America. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
When does Testing Dumb Things wipe?
One wipe a month for Testing Dumb Things: the force wipe. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. Its world went live 21 hours. Its tags carry a monthly wipe schedule.
Server Details
Is Testing Dumb Things up, and how does its uptime hold?
Tracking shows Testing Dumb Things online as of now. By its own uptime figure, the last restart was roughly 8 hours ago. 1% uptime over the last 7 full days, with 2 of 168 hours up. Rust Tracker logged it first on 13 September 2026.
Which Rust version is confirmed on Testing Dumb Things?
Rust network protocol 2635 and build 168909 on Linux is what Testing Dumb Things runs. The same protocol is required to join, and Steam updates it for you.
What is performance like on Testing Dumb Things?
Server fps held an average of 9 across the last 48 hours, never below 5. Maximum entities carried: 21,917, from buildings and deployables to everything else. It drew as much as 1,210 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.
Where does Testing Dumb Things sit?
The NA tag places Testing Dumb Things in North America, by its own listing. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 66.51.96.89:28000.
Population
Is Testing Dumb Things busy?
Testing Dumb Things is at 0 players, capacity 50. Peak of 1 in the last seven days, average 0 players. At 01:00 UTC it drew its highest average of the last 48 hours: 1 players.
Where does Testing Dumb Things sit in the server rankings?
Top 55% of all ranked servers and #1,360 in North America: Testing Dumb Things ranks #12,338 on player hours over the last seven days.
Settings
Which settings and rules are confirmed on Testing Dumb Things?
No gather rate appears in Testing Dumb Things's name. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Raiding and PvP are permitted between players. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.
Which map is confirmed for Testing Dumb Things?
The map on Testing Dumb Things is procedural, size 3,500, seed 1337, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Custom Map.
How to Join
Which steps join Testing Dumb Things?
Open the console in Rust with F1 after starting the game, then type client.connect 66.51.96.89:28000. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp50
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^m
Mods and access
^o
^z
Region
NA
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.