DWG RG-S15341Server sheetchecked 5d ago
Testing Testing
Offline NA 66.51.99.65:28010 checked 5d 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
Top 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
Coming wipes
- 7d 2hThu 5 Nov, 19:00 UTCFW
- 13d 2hWed 11 Nov, 18:29 UTC
- 27d 2hWed 25 Nov, 18:29 UTC
- 35d 2hThu 3 Dec, 19:00 UTCFW
- 41d 2hWed 9 Dec, 18:29 UTC
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 18:29 UTC14d ago | 3 | – | running | 0 |
| Sat 3 Oct, 13:58 UTC26d ago | – | – | 11.2 days | 0 |
| Tue 15 Sep, 14:33 UTC44d ago | 0 | – | 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.
Similar servers
Quick answers
Server details
How reliable is Testing Testing, and is it online now?
The current state of Testing Testing is offline, with the last sighting 5 days 19 hours ago. 46 of 168 hours up over the last 7 full days, which is 27% of the time. On 13 September 2026 is when Rust Graphs first saw it.
What location is recorded for Testing Testing?
The NA tag is how Testing Testing lists itself in North America. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 66.51.99.65:28010 is its address.
On which Rust version is Testing Testing running?
The platform is Linux and the version is Rust network protocol 2634 and build 167781 on Testing Testing. Steam updates your game, which must be on the same protocol for you to join.
Population
What does the population history show for Testing Testing?
The latest refresh records Testing Testing as offline, last seen 5 days 19 hours ago. Averaged across seven days, the player count is 0.
Against other Rust servers, where is Testing Testing placed?
The same seven-day player-hour count places Testing Testing at #1,503 within North America, #15,341 across all ranked servers and in the top 69% of them.
Wipe data
What is recorded on Testing Testing on wipe day?
The recent wipes averaged a busiest count of 2 players. 0 hours after the latest wipe, the crowd peaked.
Which times and days are wipes plotted at on Testing Testing?
Too few of Testing Testing's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 14 days 21 hours ago. Its tags give a wipe schedule of one wipe every two weeks.
Map and rules
Which rules and settings are recorded for Testing Testing?
The name of Testing Testing records no gather rate. Eight players per group: the default for the game. pve, no fighting other players, is the game mode. The server browser lists it under Modded: plugins or settings change the game. Carbon plugins are run on it. VAC is on: that is Valve's anti-cheat.
What is the map for Testing Testing?
Size 5,000 with seed 1337: that is the procedural map Testing Testing runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. Recorded map name: Custom Map.
Filters
Where does Testing Testing appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry Testing Testing are: Modded Rust servers, PvE Rust servers, plotted and Rust server list: North America. These filters on the server list return it: 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.
On Testing Testing, what is meant by each tag?
The game's server browser reads these tags from Testing Testing: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): 50 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): To join, your game must be on protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): Player fights are off; the world supplies the danger; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): The browser's listing places it under North America. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
How is Testing Testing joined?
Enter client.connect 66.51.99.65:28010 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.
Server tags
Published as mp50,ptrak,$r?,v2634,^z,^y,^b,NA,^p,gmrust,cs167781,ts8
Game
gmrust
mp50
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^b
Gameplay
^p
Mods and access
^z
^y
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.