Local Test
Offline 80.187.74.12: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
- 20/ 100
- 135/ 400
- 94/ 225
- 133/ 100
- 124/ 1000
- 5/ 700
Quick answers
Tags and filters
Where does Local Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Local Test: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on Local Test?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): It holds 2 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): The build number is 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): This server relies on Carbon for plugins — that is the tag list Local Test puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What location is Local Test in?
There is no published region for Local Test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 80.187.74.12:28015.
What's the uptime like for Local Test?
Right now Local Test is offline, having last been seen 29 days 16 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 18 September 2026.
What Rust version is Local Test on?
The version on Local Test is Rust network protocol 2633 and build 164530, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
How often does Local Test wipe?
The wipes recorded for Local Test are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 29 days 19 hours ago.
Map and rules
What settings are in place on Local Test?
The name of Local Test contains no gather rate. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Carbon plugins are running here. The server runs Valve's anti-cheat, VAC.
What's the map on Local Test?
A procedural map, generated by the game, is in play on Local Test.
Population
Is Local Test busy?
Local Test was last seen 29 days 16 hours ago and is offline as you read this.
Where does Local Test sit in the rankings?
For player hours in the last seven days, Local Test ranks #15,382, within the top – of ranked servers.
How to join
What's the process to join Local Test?
Open Rust and press F1, then type client.connect 80.187.74.12:28015. Alternatively, click Launch Rust on this page to join via Steam.