Local Test Server
Offline 149.50.208.134: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
- 0/ 100
- 77/ 400
- 60/ 245
- 129/ 100
- 152/ 1000
- 17/ 700
Quick answers
Tags and search
Where does Local Test Server appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Local Test Server are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on Local Test Server?
Local Test Server's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams cap at 8, which is the game default; v2621 (Protocol): This server runs game protocol 2621, so your game must match that version to join; cs143390 (Build): This server runs build 143390; ptrak (Networking): The network layer is RakNet, Rust's default; $rfra (Region code): Region: fra; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is Local Test Server in?
No region is published by Local Test Server, and the region code is fra. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 149.50.208.134:28015.
What's the uptime like for Local Test Server?
Local Test Server is down at the moment; it was last up 29 days 8 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 18 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Local Test Server?
Rust network protocol 2621 and build 143390 is what Local Test Server runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
How often does Local Test Server wipe?
Too few wipes are on record for Local Test Server to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 242 days 9 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to Local Test Server?
Its name does not state a gather rate for Local Test Server. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. The server does not run Valve's anti-cheat, VAC.
What's the map on Local Test Server?
Local Test Server uses a game-generated procedural map.
Population
Is Local Test Server busy?
The last sighting of Local Test Server was 29 days 8 hours ago; it is offline right now.
What position does Local Test Server hold in the server rankings?
Over the last seven days, Local Test Server is #15,391 by player hours, among the top – of all ranked servers.
Getting in
What's the process to join Local Test Server?
To join, open Rust, hit F1, and enter client.connect 149.50.208.134:28015. Or click Launch Rust on this page to open the game through Steam and connect.