Station XX-16557 · no signal
MyLocalTest
Offline 150.228.63.234:28015 checked 27d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,557
- top 70%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 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. 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
- 0.9 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 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 11:41 UTC27d ago | M0.0▼falling | 0 | – | – | running | 1 |
| Wed 30 Sep, 09:00 UTC28d ago | M0.0■steady | 1 | – | 1.1 days | 1 | |
| Tue 29 Sep, 18:20 UTC29d ago | M0.0▲rising | 1 | – | 0.6 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 MyLocalTest?
The map on MyLocalTest is procedural, produced by the game.
Which settings and rules apply on MyLocalTest?
The name of MyLocalTest gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on MyLocalTest right now?
No players are recorded on MyLocalTest at this moment; it is offline, and the last sighting was 27 days 11 hours ago.
How does MyLocalTest rank against other Rust servers?
On player hours for the past week, MyLocalTest sits at #16,557, which puts it inside the top 70% of every ranked server.
Server details
How reliably does MyLocalTest stay online?
MyLocalTest is down at the moment; the last recorded contact was 27 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 29 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does MyLocalTest run from?
No region is published by MyLocalTest. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 150.228.63.234:28015.
What build of Rust does MyLocalTest use?
On Windows, MyLocalTest runs Rust network protocol 2634 and build 166235. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on MyLocalTest?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does MyLocalTest wipe, and on which days?
No next wipe can be predicted for MyLocalTest, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 27 days 11 hours is how long the current world has been running.
Tags
What do the server tags on MyLocalTest mean?
The game's server browser reads the tags MyLocalTest publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166235 (Build): It runs game build 166235; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 MyLocalTest appear?
The Rust Server Trends lists that take in MyLocalTest are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Join the server
How do you connect to MyLocalTest?
You can connect by pressing F1 in Rust and typing client.connect 150.228.63.234:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.