Station NA-15323 · no signal
Testing Testing
Offline NA 66.51.99.65:28010 checked 5d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,323
- top 69% · #1507 in NA
- Last wipe
- 14d ago
- biweekly schedule
- Next wipe
- 7d 7h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 7h. 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
- 7d 7hThu 5 Nov, 19:00 UTCFW
- 13d 7hWed 11 Nov, 18:29 UTC
- 27d 7hWed 25 Nov, 18:29 UTC
- 35d 7hThu 3 Dec, 19:00 UTCFW
- 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 14 Oct, 18:29 UTC14d ago | M0.5▲rising | 3 | – | running | 0 | |
| Sat 3 Oct, 13:58 UTC25d ago | – | – | – | – | 11.2 days | 0 |
| Tue 15 Sep, 14:33 UTC43d ago | M0.0■steady | 0 | – | 18 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Testing Testing?
The procedural map on Testing Testing is size 5,000 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.
Which settings and rules apply on Testing Testing?
No gather rate appears in the name of Testing Testing. The group limit is 8 players, the game's default. In pve mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Testing Testing right now?
A reading taken now finds Testing Testing offline; the most recent activity was 5 days 14 hours ago. The seven-day average for this server is 0 players.
How does Testing Testing rank against other Rust servers?
Testing Testing is #1,507 in North America and #15,323 worldwide on the past week's player hours, within the top 69% of ranked servers.
Operator and location
How reliably does Testing Testing stay online?
Testing Testing is down at the moment; the last recorded contact was 5 days 14 hours ago. It was up 27% of the time across the last 7 full days: 46 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does Testing Testing run from?
The NA tag is how Testing Testing lists itself in North America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 66.51.99.65:28010.
What build of Rust does Testing Testing use?
On Linux, Testing Testing runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Testing Testing?
2 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Testing Testing run its wipes?
The prediction is taken from its tag, since Testing Testing has too few wipes on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 14 days 16 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Tags
What do the server tags on Testing Testing mean?
Tags published by Testing Testing and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): It wipes once a fortnight; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here; NA (North America): In the server browser it appears under North America. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Testing Testing appear?
The Rust Server Trends lists that take in Testing Testing are: Modded Rust servers, tracked live, Rust PvE servers and North America Rust servers. You will find it under these filters on the server list: 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.
Join the server
What steps get you onto Testing Testing?
Enter client.connect 66.51.99.65:28010 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.