Local Server1 MAIN
Offline 86.146.176.163:28015 checked 16h ago
Server instruments
last reading Wed 15:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 218 · below 20 is lag, below 10 is badEntities
48 h range 5,672–7,993 · memory 1,189 MBUptime
5 h 30 min since its last restart, at the last readingPlayers
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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 32% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 20:12 UTC13d ago | 1 | – | running | 0 |
| Tue 6 Oct, 12:20 UTC22d ago | 1 | halved by day 8 | 9.3 days | 0 |
| Wed 30 Sep, 17:39 UTC28d ago | 0 | – | 5.8 days | 1 |
| Mon 21 Sep, 17:07 UTC37d ago | 1 | held half | 9 days | 1 |
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- 103/500
- 134/100
- 151/225
- 45/700
- 5/200
- 19/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on Local Server1 MAIN?
At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. By day 8 it fell below half when it didn't.
How often does Local Server1 MAIN wipe, and when?
There is no next wipe to predict: Local Server1 MAIN wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 13 days 11 hours ago the current world was made.
Tags
How should you read the tags on Local Server1 MAIN?
Tags published by Local Server1 MAIN, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Local Server1 MAIN?
These Rust Metrics lists carry Local Server1 MAIN: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Occupancy
What position does Local Server1 MAIN hold among Rust servers?
Ranking for Local Server1 MAIN: #7,125 on seven-day player hours, top 32% of all ranked servers.
How full does Local Server1 MAIN get?
Status for Local Server1 MAIN: offline. Last seen 16 hours ago. Check: players over seven days. Average 1, peak 1. Check: 48-hour peak. 13:00 UTC, 1 players on average.
Server
Where does Local Server1 MAIN sit?
Reading: location. Local Server1 MAIN gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 86.146.176.163:28015.
What Rust version is Local Server1 MAIN on?
Rust network protocol 2635 and build 168909 on Windows is the build Local Server1 MAIN runs. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for Local Server1 MAIN?
Over the last 48 hours the average was 238 server fps; the floor was 218. Reading: 7,993 entities at the highest. That covers buildings, deployables and everything else. Reading: 1,411 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is Local Server1 MAIN, and is it online now?
Reading: offline. Local Server1 MAIN last answered 16 hours ago. Reading: uptime. About 5 hours ago it restarted, on its own count. Uptime for the last 7 full days: 21 of 168 hours, or 12%. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on Local Server1 MAIN?
Reading the name gives no gather rate for Local Server1 MAIN. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is Local Server1 MAIN on?
Size 1,500 and seed 9876513: the game generates the procedural map on Local Server1 MAIN from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
How do you connect to Local Server1 MAIN?
Check: join. Open Rust, press F1, then enter client.connect 86.146.176.163:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.