Station NA-16717 · no signal
TestSrv1
Offline NA 143.59.126.130:28002 checked 29d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,717
- top 70% · #1678 in NA
- Last wipe
- 29d ago
- monthly schedule
- Next wipe
- 6d 21h
- 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers, top 84% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 21h. The force wipe · high confidence
- usual gap
- 0.3 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 6d 21hThu 5 Nov, 19:00 UTCFW
- 34d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 30 Sep, 20:59 UTC29d ago | M0.0▼falling | 0 | – | – | running | 1 |
| Wed 30 Sep, 00:04 UTC29d ago | M0.0▲rising | 1 | – | 0.9 days | 0 | |
| Tue 29 Sep, 18:02 UTC30d ago | M0.0▲rising | 1 | – | 0.3 days | 0 | |
| Tue 29 Sep, 11:37 UTC30d ago | M0.0■steady | 1 | – | 0.3 days | 1 | |
| Tue 29 Sep, 02:53 UTC30d ago | M0.0■steady | 1 | – | 0.4 days | 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 pageMap and rules
Which map is running on TestSrv1?
TestSrv1 uses a procedural map, which the game generates.
Which settings and rules apply on TestSrv1?
The name of TestSrv1 gives no gather rate. Groups hold up to 8 players, which is the default for the game. In pve mode, no combat against other players. Under Community in the server browser, it runs as a community server. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on TestSrv1?
TestSrv1 is not responding at this moment and is offline, last seen 29 days ago.
How does TestSrv1 rank against other Rust servers?
For player hours across the last seven days, TestSrv1 takes #16,717 overall and #1,678 in North America, inside the top 70% of all ranked servers.
Operator and location
How reliably does TestSrv1 stay online?
No contact with TestSrv1 right now, and the last recorded contact was 29 days ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does TestSrv1 run from?
The NA tag is how TestSrv1 lists itself in North America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 143.59.126.130:28002 is the address it uses.
What build of Rust does TestSrv1 use?
Rust network protocol 2633 and build 165217 on Linux is what TestSrv1 runs. 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 TestSrv1?
The recent wipes averaged a busiest count of 1 players. 1 hours after the latest wipe, the crowd peaked.
How often does TestSrv1 wipe, and on which days?
At the force wipe each month TestSrv1 wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 29 days is how long the current world has been running. A monthly wipe schedule is published in its tags.
Tags
What do the server tags on TestSrv1 mean?
These are the tags TestSrv1 publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), 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 TestSrv1 appear?
These Rust Server Trends lists include TestSrv1: Rust community servers without the side modes, Rust PvE servers and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Connecting
How do you connect to TestSrv1?
To join, enter client.connect 143.59.126.130:28002 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.