Local
Offline 62.106.78.113:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
2% 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- 117/500
- 134/100
- 117/225
- 47/700
- 6/200
- 24/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Local follow?
The rhythm of Local'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 in play was created 40 days 1 hours ago.
Tag meanings
Which tags does Local carry, and what do they mean?
These are the tags Local publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Local appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Local: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Population
What position does Local hold among Rust servers?
Player hours over seven days put Local at #14,090, in the top – of all ranked servers.
How full does Local get?
Reading for Local: offline at this moment; last seen 40 days ago.
Server details
Which location does Local run from?
No region tag on Local. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 62.106.78.113:28015.
What Rust version is Local on?
Reading: Local, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
Is Local up, and how often does it stay up?
Reading: offline. Local last answered 40 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 18 September 2026.
Map and rules
What settings and rules apply on Local?
Reading the name gives no gather rate for Local. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.
What map is Local on?
Procedural map on Local, made by the game's generator.
Connection
How do you connect to Local?
Press F1 in Rust and enter client.connect 62.106.78.113:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.