RS-15986Community server
Local_Test
Offline 104.28.217.175:28015 checked 1d 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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 09:19 UTC1d ago | – | – | running | 0 |
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.
Quick answers
From the figures on this page.
Population
How many players are usually on Local_Test?
Currently, Local_Test is offline; the last sighting was 36 hours ago. The average over the last seven days comes to 0 players.
Where does Local_Test sit in the rankings?
Ranked #15,986 on seven-day player hours, Local_Test is in the top 71% of all ranked servers.
Tags, lists, and filters
Where does Local_Test show up in Top Rust Servers lists and filters?
These Top Rust Servers lists count Local_Test among their servers: Best Rust community servers. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the tags on Local_Test?
gmrust (Game mode): Survival follows the standard Rust ruleset; mp10 (Max players): Player slots: 10; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must be on protocol 2634; cs167584 (Build): Running game build 167584; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set are the tags Local_Test publishes, and the game's server browser reads them. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.
Rules, settings, and map
What is the map on Local_Test?
A procedural map, created by the game, is in use on Local_Test.
What does Local_Test run for rules and settings?
The name Local_Test does not state a gather rate. Up to 8 players per group, as the game defaults. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser shows it under Community. VAC anti-cheat is inactive.
Server details
What Rust version is Local_Test on?
Local_Test uses Rust network protocol 2634 and build 167584 with Windows as its system. Your game needs the same protocol to connect; Steam takes care of updating it.
What is the location of Local_Test?
A region is not published by Local_Test. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. It answers at 104.28.217.175:28015.
How reliable is Local_Test?
The server Local_Test is down at the moment, with its last appearance 36 hours ago. It spent 2 of the last 168 hours online across 7 days, giving 1% uptime. Its first appearance in Top Rust Servers was on 16 September 2026.
Wipe details
On what schedule does Local_Test wipe?
Too few wipes are recorded for Local_Test to establish a rhythm. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. Its world was last replaced 37 hours ago.
Connection
What is the process to join Local_Test?
Use the console: open Rust, press F1, and type client.connect 104.28.217.175:28015. Or simply click Launch Rust here; it opens the game through Steam and connects you.