Rust Data LabData lab · live
Live readings Servers11,740 Players65,587 Populated3,350 Fresh wipes · 3h201 Sampled every 5 min

Element card · group Modded · atomic number 4,489, its rank

in.high

Online 116.58.190.230:28015 checked 7m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak 2
Rank · atomic number#4,489top 20%
Last wipe15d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.511.5200:0009:0019:0004:0013:0022:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
05010015020000:0009:0019:0004:0013:0022: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Reaction kinetics

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 gap7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Wed 14 OctFri 2 OctWed 30 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 11:50 UTC15d ago 2 – running 2
Fri 2 Oct, 08:15 UTC27d ago 1 held half 12.1 days 0
Wed 30 Sep, 13:42 UTC29d ago 1 – 1.8 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
  1. 1 Sh ShockRust | Bl… 32
    ShockRust | Blue | NoLimit no group limit · 149 on average 32/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 128
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 128/ 100
  3. 3 Re RETRO RUST #1 … 49
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average 49/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 16
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average 16/ 700
  5. 5 Ru 404 RUST 2Х|ДЛ… 50
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 93 on average 50/ 700
  6. 6 Ru RustSpain.com … 238
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average 238/ 260

Quick answers

from the figures on this page

Settings and map

What map is in play on in.high?

The map on in.high is procedural at size 4,000 with seed 814592164, made by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

How is in.high configured, and what rules apply?

Nothing in the name of in.high gives a gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running on it. Anti-cheat is on: Valve's VAC.

Server facts

Which location is in.high based in?

No region is published by in.high. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 116.58.190.230:28015 is the address it uses.

Which Rust version is in.high on?

On Windows, in.high is running Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam takes care of updating it.

Does in.high stay up, and how reliable is its uptime?

At the moment, in.high is online. About 6 days 20 hours ago is when it last restarted, based on its uptime. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

Is in.high known for smooth running?

The last 48 hours show an average of 132 server fps and a minimum of 103. The maximum entity count was 95,733, covering buildings, deployables and all else in the world. The highest memory usage was 3,738 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipes and resets

What is the wiping pattern on in.high?

With no fixed rhythm, in.high wipes at irregular times, so the next wipe cannot be predicted. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it is running now dates from 15 days 11 hours ago.

What does a typical wipe day on in.high involve?

Recent wipes on average reached 1 players at their busiest. Peak numbers on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

Tags, lists

Which meanings sit behind the tags on in.high?

These are the tags in.high makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp10 (Max players): Player slots: 10; ts8 (Group limit): 8 per team, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded; modded (Modded): Because plugins or settings change the game, it is filed under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does in.high come up?

The Rust Data Lab lists that include in.high are: Modded Rust servers, measured. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player numbers

Against other Rust servers, where does in.high place?

Player hours over the last week put in.high at #4,489, inside the top 20% of ranked servers.

What does the current player count on in.high tell you?

Of 10 slots, 0 are taken on in.high right now. The week's figures average 0 players and top out at 2. The busiest point in the last 48 hours came at 12:00 UTC, averaging 2 players.

Connection

What is the way to join in.high?

Open the console with F1 in Rust and type client.connect 116.58.190.230:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp10
Max players Player slots: 10.
ts8
Group limit 8 per team, the default the game ships with.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under Modded.
modded
Modded Because plugins or settings change the game, it is filed 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.