Offline NA 66.51.99.65:28010 checked 5d ago
Testing Testing
Connect
srv = rust.server("66.51.99.65:28011")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 7h | Wed 11 Nov, 18:29 UTC | wipe |
| 2 | 27d 7h | Wed 25 Nov, 18:29 UTC | wipe |
| 3 | 35d 7h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 7h | Wed 9 Dec, 18:29 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 18:29 UTC14d ago | 3 | NaN | running | 0 |
| 1 | Sat 3 Oct, 13:58 UTC25d ago | NaN | NaN | 11.2 days | 0 |
| 2 | Tue 15 Sep, 14:33 UTC43d ago | 0 | NaN | 18 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.
display(srv.map, srv.info())Map
5000 · seed 1337
- map
- Custom Map
- size
- 5000
- seed
- 1337
Server
srv.info()- address
- 66.51.99.65:28010
- region
- NA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 14 Oct 2026, 18:29 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 116/2000 |
| 1 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 22/200 |
| 2 | Orange Dream | Cozy PvE/RP | No KOS | NA · groups of 8+ · biweekly · 33 on average | 10/200 |
| 3 | LuffyRust Texas USA - 10xPvE|NoBP|Kits|Skins|Backpacks|Purge No | NA · groups of 12+ · biweekly · 14 on average | 8/30 |
| 4 | ZOMBZ SPOOKY PVE|Hawk Ridge Island|Zombies|Kits|Backpack|No Los | NA · groups of 12+ · biweekly · 12 on average | 3/100 |
| 5 | US Markiii-Rust PVE | 900+ Raids | Custom Weapons | Markiii-Pro | NA · groups of 8+ · biweekly · 6 on average | 1/50 |
Quick answers
From the figures on this page.
Population
What position does Testing Testing take in the server rankings?
Player hours over the last seven days: #15,323 for Testing Testing, #1,507 in North America, within the top 69% of the ranked set.
What population does Testing Testing carry?
The current row shows Testing Testing offline; the last response was 5 days 14 hours ago. Over the last seven days it averaged 0 players.
About the server
What is the Rust version on Testing Testing?
The build is Rust network protocol 2634 and build 167781 on Linux, run by Testing Testing. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Testing Testing, and is it up?
The latest sample has Testing Testing offline, with a last sighting 5 days 14 hours ago. 46 of 168 hours up over the last 7 full days, or 27%. Rust Data logged it first on 13 September 2026.
Where does Testing Testing sit?
The NA tag is what Testing Testing uses to list itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 66.51.99.65:28010 is its address.
Settings and map
Which settings and rules does Testing Testing run?
No gather rate appears in the name: Testing Testing. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
What is the map on Testing Testing?
Testing Testing runs a procedural map of size 5,000 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipes and dates
When does Testing Testing wipe, and on what schedule?
The prediction follows the tag, because Testing Testing's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 14 days 16 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.
What is wipe day on Testing Testing like?
Recent wipes averaged 2 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold Testing Testing, and which filters?
These Rust Data lists include Testing Testing: Modded Rust servers, Rust PvE servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on Testing Testing hold?
These tags are published by Testing Testing and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon; NA (North America): North America is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Testing Testing?
In Rust, F1 opens the console: type client.connect 66.51.99.65:28010. Launch Rust on this page does the same by opening the game through Steam and connecting.