StatusLive Servers online11,701 Players54,561 Populated3,263 Wiped · 3 h144 Interval5 min Date29 OCT 2026

DWG RG-S7117Server sheetchecked 18h ago

Local Server1 MAIN

Offline 86.146.176.163:28015 checked 18h ago

moddedoxide
Connect
Players now 0/ 10 0% full
7-day average1peak 1
Rank#7,117top 32%
Last wipe13d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75111:0014:0017:0009:0012:0015:00

Hourly average and peak, UTC.

Fig. 1Players on Local Server1 MAIN
Fig. 2

Server performance

010020030040011:0014:0017:0009:0012:0015:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 32% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 8

The first 48 hours of its last wipes

Thu 15 OctTue 6 OctWed 30 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 149 on average
130 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
122 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
192 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
73 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
10 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
17 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is Local Server1 MAIN, and is it online now?

Local Server1 MAIN is offline at this moment; 18 hours ago is when it was last seen. About 5 hours ago is when it last restarted, measured from the uptime it reports. 21 of 168 hours up over the last 7 full days, which is 12% of the time. The first sighting of it by Rust Graphs was on 17 September 2026.

How does Local Server1 MAIN perform, as measured?

The last 48 hours give an average of 238 server fps and a floor of 218. Counted at its highest: 7,993 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 1,411 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Local Server1 MAIN?

No region is published by Local Server1 MAIN. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 86.146.176.163:28015 is its address.

On which Rust version is Local Server1 MAIN running?

On Windows, Local Server1 MAIN runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Player data

What player count is recorded on Local Server1 MAIN?

Local Server1 MAIN is not responding at the latest refresh; the last record of it online is 18 hours ago. Averaged across seven days, the player count is 1, with a peak of 1. Averaged over the last 48 hours, the player count is highest at 13:00 UTC: 1 players.

In the rankings, which position does Local Server1 MAIN hold?

Player hours over seven days place Local Server1 MAIN at #7,117, within the top 32% of ranked servers.

Schedules

What happens on Local Server1 MAIN on the day of a wipe?

The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 50% of its recent wipes. In the other cases the crowd was below half by day 8.

Which times and days are wipes plotted at on Local Server1 MAIN?

There is no next wipe to predict at Local Server1 MAIN, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 13 days 13 hours ago.

Settings

Which settings does Local Server1 MAIN run, and what rules?

No gather rate is stated in the name of Local Server1 MAIN. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

Which map has Local Server1 MAIN loaded?

Size 1,500 with seed 9876513: that is the procedural map Local Server1 MAIN runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Lists and filters

Where does Local Server1 MAIN appear among the Rust Graphs lists and filters?

These Rust Graphs lists include Local Server1 MAIN: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meaning is attached to each tag on Local Server1 MAIN?

The game's server browser reads these tags from Local Server1 MAIN: gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

What is the way to connect to Local Server1 MAIN?

Connect with client.connect 86.146.176.163:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp10
Max players The slot count is 10.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

KeyTag string decoded