Testing Dumb Things
Online NA 66.51.96.89:28000 checked 35m ago
Server instruments
last reading Thu 23:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 5 · below 20 is lag, below 10 is badEntities
48 h range 3,069–21,917 · memory 1,002 MBUptime
10 h 28 min since its last restart, at the last readingPlayers
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 17h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 17hFW
- WPT 2Thu 3 Dec, 19:00 UTC34d 17hFW
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- 18/175
- 9/90
- 5/1000
- 2/15
- 1/50
- 1/50
Quick answers
from the figures on this pageWipe timing
What wipe timing does Testing Dumb Things follow?
With the force wipe, once a month, Testing Dumb Things wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 23 hours ago. Its tags carry a monthly wipe schedule.
Tag meanings
How should you read the tags on Testing Dumb Things?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): The server browser files it under North America from Testing Dumb Things. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Testing Dumb Things?
These Rust Metrics lists carry Testing Dumb Things: Modded Rust servers, checked live and North America: server readout. Reading: server list filters. It comes up under 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.
Player count
What position does Testing Dumb Things hold among Rust servers?
Top 55% of all ranked servers: Testing Dumb Things takes #12,340 on seven-day player hours and #1,358 in North America.
What player count does Testing Dumb Things carry?
0 of 50 slots are filled on Testing Dumb Things right now. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 01:00 UTC over the last 48 hours.
Operator and location
What location is Testing Dumb Things hosted in?
Testing Dumb Things gives North America as its location, with the NA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 66.51.96.89:28000.
What Rust version is Testing Dumb Things on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Testing Dumb Things. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on Testing Dumb Things within range?
Reading: 8 server fps on average across the last 48 hours. It never dropped below 5. Reading: 21,917 entities at the highest. That covers buildings, deployables and everything else. Reading: 1,210 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on Testing Dumb Things, and is it online?
Check: connection. Testing Dumb Things is online at this moment. By its reported uptime, the last restart was roughly 10 hours ago. Uptime for the last 7 full days: 26 of 168 hours, or 15%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
How is Testing Dumb Things configured, and what rules are in force?
Reading the name gives no gather rate for Testing Dumb Things. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is Testing Dumb Things on?
Check: map. Procedural, size 3,500, seed 1337, generated by the game on Testing Dumb Things. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.
How to join
What do you do to join Testing Dumb Things?
Check: join. Open Rust, press F1, then enter client.connect 66.51.96.89:28000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.