Local_Test
Offline 190.114.39.185:28015 checked 41d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestBx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What is the wipe schedule on Local_Test?
Local_Test has too few wipes on record yet for its rhythm to show. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 41 days 10 hours ago.
Player counts
How busy is Local_Test?
Last seen 41 days 10 hours ago, Local_Test is offline at the moment.
How does Local_Test rank against other Rust servers?
Player hours over seven days put Local_Test at #15,420, in the top – of ranked servers.
Rules and settings
Which map does Local_Test run?
The game generates the procedural map on Local_Test.
What are the rules and settings on Local_Test?
The name Local_Test does not specify a gather rate. The group limit is 8 players, which is the game's default. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. You will find it under Community in the server browser; it is a community server. The server has VAC, Valve's anti-cheat, turned off.
Location and uptime
Which version of Rust does Local_Test run?
Rust network protocol 2633 and build 164530 on Windows is what Local_Test runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Local_Test online, and how reliable is it?
Local_Test is down just now; the last sighting was 41 days 10 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. Rust Heatmap has had it on record since 18 September 2026.
Where is Local_Test located?
No region is published by Local_Test. Rust Heatmap shows the location a server states. It does not look up the machine's location. 190.114.39.185:28015 is its address.
Lists and filters
Which Rust Heatmap lists and filters include Local_Test?
Best Rust community servers are the Rust Heatmap lists that Local_Test fits. These are the filters that return it on the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What do the server tags on Local_Test mean?
These are the tags Local_Test publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): The server runs game protocol 2633, so your game has to match it; cs164530 (Build): Build 164530; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join Local_Test?
Enter client.connect 190.114.39.185:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.