Skip to the story

Live edition42,162 playing on 11,632 servers

Rust Insights

Server profile

Local Server1 MAIN

Offline, with 0 of 10 players on; ranked #7,125 of every public Rust server, the top 32%. It last wiped 13d ago.

Filed under moddedoxide
Launch Rust and join
0/ 10 players now 0% full
17-day averagepeak 1
#7,125ranktop 32%
13d agolast wipeno schedule published
–next wipeno rhythm it keeps

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
00.250.50.75110:0013:0017:0022:0012:0015:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

010020030040010:0013:0017:0022:0012:0015:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

The wipe cycle

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.

9 days usual gap between real wipes
67% on rhythm of its recent wipes
1 wipe-day peak players, last three wipes
50% crowd held else halves by day 8

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

Thu 15 OctTue 6 OctWed 30 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

The record

Wipes

Every wipe we saw, 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

Note: 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.

If you like this one

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 150 on average102/500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average120/225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average46/700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average20/1000

The short version

Quick answers

From the figures on this page.

Wipe cycle

What should you expect on wipe day at Local Server1 MAIN?

Recent wipes peaked at 1 players on average. The peak crowd on this wipe came 0 hours after it started. In 50% of recent wipes, more than half the peak was still playing at the next wipe. The cases that did not hold saw the crowd fall below half by day 8.

When does Local Server1 MAIN wipe, and how often?

Local Server1 MAIN wipes at times that vary, so its next wipe cannot be predicted. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. 13 days 11 hours have passed since its current world was created.

Server

How well does Local Server1 MAIN perform?

Server fps averaged 238 over 48 hours; the lowest reading was 218. At its highest the entity count reached 7,993: buildings, deployables and everything else. Memory use peaked at 1,411 MB. What players feel as lag comes from low fps and an entity count on the rise.

On what version does Local Server1 MAIN currently run?

Rust network protocol 2635 and build 168909 on Windows is what Local Server1 MAIN runs. The same protocol is required to join, and Steam takes care of updating it.

Has Local Server1 MAIN stayed online, and is it up now?

Local Server1 MAIN is offline at the moment; the last time it was seen was 16 hours ago. The uptime it reports puts the last restart at about 5 hours ago. It spent 21 of the last 7 full days' 168 hours up, 12% of the time. On 17 September 2026 is when Rust Insights first saw it.

Where does Local Server1 MAIN run from?

A region is not published by Local Server1 MAIN. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. You can reach it at 86.146.176.163:28015.

Tags

Which meanings sit behind the tags on Local Server1 MAIN?

The tags gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded is its listing, because plugins or settings change how the game plays are what Local Server1 MAIN publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

On which Rust Insights lists does Local Server1 MAIN appear?

The Rust Insights lists that carry Local Server1 MAIN are Modded Rust servers, explained. 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.

Population

How many players are on Local Server1 MAIN right now, and how does that number move?

The last time Local Server1 MAIN was seen online was 16 hours ago, and it is offline now. Over the past week it peaked at 1 and averaged 1 players. The busiest point of the last 48 hours fell at 13:00 UTC, averaging 1 players.

In the ranking of Rust servers, where does Local Server1 MAIN place?

Player hours over seven days put Local Server1 MAIN at #7,125, within the top 32% of the ranked field.

Map and rules

How is Local Server1 MAIN configured, and what rules apply?

No gather rate appears in the name of Local Server1 MAIN. The default of 8 players per group is what applies here. survival is the game mode, the standard game: gather, build, raid. Players may raid and fight one another. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Oxide of them. The server has Valve's VAC anti-cheat switched on.

Which map is live on Local Server1 MAIN?

Local Server1 MAIN runs a procedural map of size 1,500 with seed 9876513, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.

Connecting

What is the way to join Local Server1 MAIN?

Type client.connect 86.146.176.163:28015 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam.

The small print

Server tags

What each one means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams cap at 8.
v2635
Protocol To join you need the same version; protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded is its listing, because plugins or settings change how the game plays.

Note: 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.