Station NA-15215 · no signal
testing
Offline NA 153.66.141.225:28015 checked 15d ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,215
- top 71% · #1545 in NA
- Last wipe
- 19d ago
- weekly schedule
- Next wipe
- 1d 16h
- Sat 31 Oct, 15:49 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers, top 84% in NA, and #376 of the duo servers (top 87%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Saturday 31 October, 15:49 UTC, in 1d 16h. Its weekly schedule tag · low confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 1d 16hSat 31 Oct, 15:49 UTC
- 6d 19hThu 5 Nov, 19:00 UTCFW
- 8d 16hSat 7 Nov, 15:49 UTC
- 15d 16hSat 14 Nov, 15:49 UTC
- 22d 16hSat 21 Nov, 15:49 UTC
- 29d 16hSat 28 Nov, 15:49 UTC
- 34d 19hThu 3 Dec, 19:00 UTCFW
- 36d 16hSat 5 Dec, 15:49 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 10 Oct, 15:49 UTC19d ago | M0.0■steady | 1 | – | running | 1 |
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 pageServer rules
Which settings and rules apply on testing?
You will find no gather rate in the name of testing. 2 players is the most a group can hold (duo). survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on testing right now?
testing is not responding at this moment and is offline, last seen 15 days 20 hours ago.
How does testing rank against other Rust servers?
For player hours across the last seven days, testing takes #15,215 overall and #1,545 in North America, inside the top 71% of all ranked servers. Within duo, it places #376.
Operator and location
How reliably does testing stay online?
No contact with testing right now, and the last recorded contact was 15 days 20 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 9 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is testing hosted?
With its NA tag, 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. 153.66.141.225:28015 is the address it uses.
Which Rust version is testing running?
On Windows, testing runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on testing?
On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked.
How often does testing wipe, and on which days?
Its schedule cannot be confirmed, as too few of testing's wipes are on record; the prediction follows its tag instead. The date of its next wipe is Saturday 31 October at 15:49 UTC. It has run its current world for 19 days 7 hours. A weekly wipe schedule is published in its tags.
Server tags
What do the server tags on testing mean?
Tags published by testing and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp20 (Max players): 20 slots are available; ts2 (Group limit): The team limit is 2; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): It runs game build 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^w (Weekly): Wipes happen weekly; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here; NA (North America): The server browser files it under North America. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does testing appear?
These Rust Server Trends lists include testing: Duo Rust servers, group limit 2, Modded Rust servers, tracked live and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly.
Connecting
How do you connect to testing?
Enter client.connect 153.66.141.225:28015 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.