My Local Test Server
Offline 115.131.30.27:28015 checked 29d ago
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. 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 wipes
- 23/ 100
- 129/ 400
- 80/ 225
- 126/ 100
- 121/ 1000
- 6/ 700
Quick answers
Tags and search
Where does My Local Test Server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include My Local Test Server: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on My Local Test Server?
My Local Test Server's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp5 (Max players): It holds 5 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163493 (Build): This server runs build 163493; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
About the server
What location is My Local Test Server in?
No region comes from My Local Test Server. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 115.131.30.27:28015.
How reliable is My Local Test Server?
My Local Test Server is down at the moment; it was last up 29 days 18 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 13 September 2026.
What is the Rust version for My Local Test Server?
Rust network protocol 2633 and build 163493 is what My Local Test Server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
What schedule does My Local Test Server follow for wipes?
The wipes recorded for My Local Test Server are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 38 days 17 hours is how long ago this world came into being.
Settings and map
What settings are in place on My Local Test Server?
No gather rate appears in the name of My Local Test Server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. The server does not run Valve's anti-cheat, VAC.
Which map is active on My Local Test Server?
The map on My Local Test Server is procedural, made by the game.
Player stats
How many players are on My Local Test Server?
Right now My Local Test Server is offline, with its last appearance 29 days 18 hours ago.
Where does My Local Test Server sit in the rankings?
For player hours in the last seven days, My Local Test Server ranks #13,254, within the top – of ranked servers.
Join info
What's the process to join My Local Test Server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 115.131.30.27:28015.