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 8h. The force wipe · high confidence
- usual gap
- 14.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 2players, last three wipes
Coming wipes
- in 7d 8hThu 5 Nov, 19:00 UTCFW
- in 13d 7hWed 11 Nov, 18:29 UTC
- in 27d 7hWed 25 Nov, 18:29 UTC
- in 35d 8hThu 3 Dec, 19:00 UTCFW
- in 41d 7hWed 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 |
|---|---|---|---|---|
14 OCT 2026Wed 14 Oct, 18:29 UTC14d ago |
3 | – | running | 0 |
3 OCT 2026Sat 3 Oct, 13:58 UTC25d ago |
– | – | 11.2 days | 0 |
15 SEP 2026Tue 15 Sep, 14:33 UTC43d 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Settings and map
On Testing Testing, which rules and settings apply?
No gather rate appears in the name Testing Testing. The group limit is 8 players, the game's default. Filed under pve, no combat between players. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Carbon. VAC is on: Valve's anti-cheat is enabled.
What is the map on Testing Testing?
Testing Testing runs a procedural map of size 5,000 with seed 1337, generated by the game. You can view the map on RustMaps from this page, as the same size and seed give the same map. Filed under map name: Custom Map.
Lists and filters
Where does Testing Testing appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include Testing Testing are Modded Rust servers, filed by play style, Rust PvE servers, filed A to Z and North American Rust servers. These filters on the server list bring it up: 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.
What is meant by the tags on Testing Testing?
Filed under these tags, as published by Testing Testing and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): The queue ceiling sits at 50; ts8 (Group limit): Game default applies: teams of up to 8; v2634 (Protocol): Your client must run protocol 2634 to connect; cs167781 (Build): It runs build 167781; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^b (Biweekly): The cycle runs to a wipe every fortnight; ^p (PvE): No fighting between players: the danger comes from the world; ^z (Modded): This one is Modded, since plugins or settings change how it plays; ^y (Carbon): Plugins run through Carbon; NA (North America): Server browser region: North America. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
What happens on wipe day at Testing Testing?
At their busiest, its recent wipes drew 2 players on average. The latest wipe peaked 0 hours in.
Which wipe timetable does Testing Testing follow?
Its schedule is unconfirmed: too few of Testing Testing's wipes are on record, and the prediction follows the tag. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, taken by every Rust server. Its present world dates from 14 days 16 hours. Filed in its tags: a wipe schedule of every two weeks.
Players and ranking
How is Testing Testing ranked compared with the rest?
On seven-day player hours, Testing Testing takes #15,338 overall and #1,508 in North America, within the top 69% of ranked servers.
Is Testing Testing quiet or crowded?
The last check found Testing Testing offline, last seen 5 days 13 hours ago. 0 players is the average over the past seven days.
Server facts
What version does Testing Testing use?
Rust network protocol 2634 and build 167781, on Linux, is what Testing Testing runs. Steam keeps your game updated, but the protocol must match for you to join.
Is Testing Testing reachable, and does it stay up?
The server is down at this moment; the last sighting of Testing Testing was 5 days 13 hours ago. Of the last 7 full days, 46 of 168 hours were up, 27% of the time. On 13 September 2026 it was first seen by Rust Server Index.
Which region is Testing Testing in?
Testing Testing gives North America as its location and the tag NA. Rust Server Index takes the server's word for its location and does not look up the machine's position. You will reach it at 66.51.99.65:28010.
Connecting
How can you connect to Testing Testing?
Enter client.connect 66.51.99.65:28010 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
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.