Local_Test
Offline 190.114.39.185:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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- 239/275
- 321/350
- 480/8
- 797/1000
- 49/100
- 889/950
Quick answers
from the figures on this pageReset cycle
How often does Local_Test wipe, and when?
To tell the rhythm of Local_Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 41 days 17 hours ago.
Tag meanings
How should you read the tags on Local_Test?
These are the tags Local_Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Local_Test appear in Rust Metrics lists and filters?
On Rust Metrics, Local_Test sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does Local_Test sit in the rankings?
Ranking for Local_Test: #15,420 on seven-day player hours, top – of all ranked servers.
What player count does Local_Test carry?
Local_Test is not responding; status offline, last seen 41 days 16 hours ago.
Server details
Where does Local_Test sit?
No region comes from Local_Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 190.114.39.185:28015.
What Rust version is Local_Test on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by Local_Test. Check: protocol. To join, your game must match; Steam handles the update.
Is Local_Test up, and how often does it stay up?
Local_Test reports offline. The last reading came 41 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 September 2026.
Rules and settings
What settings and rules apply on Local_Test?
No gather rate appears in the name: Local_Test. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.
Which map is live on Local_Test?
Procedural map on Local_Test, made by the game's generator.
Join
How do you connect to Local_Test?
Check: join. Open Rust, press F1, then enter client.connect 190.114.39.185:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.