Local Test Server
Offline 79.186.61.92:28015 checked 45d 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- 410/500
- 249/300
- 43/250
- 31/250
- 73/100
- 90/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does Local Test Server follow?
The rhythm of Local Test Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 45 days 11 hours ago.
Lists and filters
Which tags does Local Test Server carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from Local Test Server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Local Test Server?
On Rust Metrics, Local Test Server 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
How full does Local Test Server get?
Reading for Local Test Server: offline at this moment; last seen 45 days 11 hours ago.
Operator and location
Which location does Local Test Server run from?
No region tag on Local Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 79.186.61.92:28015.
What Rust version is Local Test Server on?
Reading: Local Test Server, Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is Local Test Server, and is it online now?
Reading: offline. Local Test Server last answered 45 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
What settings and rules apply on Local Test Server?
Reading the name gives no gather rate for Local Test Server. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.
Which map is live on Local Test Server?
Procedural map on Local Test Server, made by the game's generator.
Connection
How do you connect to Local Test Server?
Check: join. Open Rust, press F1, then enter client.connect 79.186.61.92:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.