Station XX-14643 · no signal
My Local Test Server
Offline 193.115.97.36:28015 checked 15d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,643
- top 67%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 10.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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 |
|---|---|---|---|---|---|---|
| Tue 13 Oct, 10:50 UTC15d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 2 Oct, 16:21 UTC26d ago | M0.0▲rising | 1 | held half | 10.8 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 My Local Test Server?
The map on My Local Test Server is procedural, produced by the game.
Which settings and rules apply on My Local Test Server?
You will find no gather rate in the name of My Local Test Server. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched off.
Live population
How many players are recorded on My Local Test Server right now?
My Local Test Server is not responding at this moment and is offline, last seen 15 days 8 hours ago.
How does My Local Test Server rank against other Rust servers?
Over the last seven days, My Local Test Server recorded enough player hours to reach #14,643 worldwide, placing it in the top 67% of all ranked servers.
Server facts
How reliably does My Local Test Server stay online?
No contact with My Local Test Server right now, and the last recorded contact was 15 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 20 September 2026.
Which region does My Local Test Server run from?
No region is published by My Local Test Server. 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 193.115.97.36:28015.
Which Rust version is My Local Test Server running?
Rust network protocol 2634 and build 167231 on Windows is what My Local Test Server runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on My Local Test Server?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
On what timetable does My Local Test Server run its wipes?
Too few wipes of My Local Test Server are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 15 days 8 hours.
Lists and tags
What do the server tags on My Local Test Server mean?
The game's server browser reads the tags My Local Test Server publishes: gmrust (Game mode): Survival in standard Rust; mp5 (Max players): The server has 5 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; cs167231 (Build): It runs game build 167231; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does My Local Test Server appear?
The Rust Server Trends lists that take in My Local Test Server are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto My Local Test Server?
To join, enter client.connect 193.115.97.36:28015 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.