Station XX-14859 · no signal
My Local Testing Server
Offline 50.25.73.37:28015 checked 33d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,859
- top 64%
- Last wipe
- 37d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.2 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 22 Sep, 13:28 UTC37d ago | M0.0■steady | 1 | – | running | 1 | |
| Mon 21 Sep, 16:03 UTC38d ago | M0.0■steady | 1 | – | 0.9 days | 1 | |
| Sun 20 Sep, 04:19 UTC39d ago | M0.0■steady | 1 | – | 1.5 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 My Local Testing Server?
My Local Testing Server uses a procedural map, which the game generates.
Which settings and rules apply on My Local Testing Server?
The name of My Local Testing Server gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. 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 My Local Testing Server right now?
My Local Testing Server is not responding at this moment and is offline, last seen 33 days 17 hours ago.
How does My Local Testing Server rank against other Rust servers?
Over the last seven days, My Local Testing Server recorded enough player hours to reach #14,859 worldwide, placing it in the top 64% of all ranked servers.
Operator and location
How reliably does My Local Testing Server stay online?
As recorded now, My Local Testing Server is not reachable, the last contact having been 33 days 17 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 20 September 2026.
Which region does My Local Testing Server run from?
A region is not published by My Local Testing Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 50.25.73.37:28015.
Which Rust version is My Local Testing Server running?
My Local Testing Server is running Rust network protocol 2633 and build 164530 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on My Local Testing Server?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does My Local Testing Server wipe, and on which days?
No next wipe can be predicted for My Local Testing Server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 37 days 6 hours.
Server tags
What do the server tags on My Local Testing Server mean?
These are the tags My Local Testing Server publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): Game build: 164530; 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; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 My Local Testing Server appear?
These Rust Server Trends lists include My Local Testing Server: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
What steps get you onto My Local Testing Server?
Enter client.connect 50.25.73.37: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.