Rust Server TrendsSeismic network · station log
Recording Stations11,737 Players52,204 Active3,347 Wipes · 3 h125 48 h

Station XX-4551 · recording

in.high

Online 116.58.190.230:28015 checked 10m ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#4,551
top 20%
Last wipe
14d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-4551 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 10 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Wed 11:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5200:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020000:0009:0018:0003:0012: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Expected events

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 gap
7 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 14 Oct, 11:50 UTC14d ago M0.0steady 2 – running 2
Fri 2 Oct, 08:15 UTC26d ago M0.0rising 1 held half 12.1 days 0
Wed 30 Sep, 13:42 UTC28d ago M0.0steady 1 – 1.8 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
53/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
124/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
41/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average
52/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
8/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
7/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on in.high?

Generated by the game, the map on in.high is procedural, size 4,000 with seed 814592164. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on in.high?

You will find no gather rate in the name of in.high. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on in.high?

At this moment, in.high records 0 players across 10 slots. The seven-day average is 0 players, with a peak of 2. The busiest point in the last 48 hours came at 12:00 UTC, averaging 2 players.

How does in.high rank against other Rust servers?

On player hours for the past week, in.high sits at #4,551, which puts it inside the top 20% of every ranked server.

Server details

How reliably does in.high stay online?

As recorded now, in.high is running. The uptime it reports puts its last restart about 5 days 20 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does in.high perform under load?

Its average server fps over the last 48 hours was 133, and it never dropped below 103. Buildings, deployables and all the rest of the world's entities brought it to a high of 95,629. Its highest memory use was 3,559 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does in.high run from?

A region is not published by in.high. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 116.58.190.230:28015.

Which Rust version is in.high running?

in.high is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on in.high?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

On what timetable does in.high run its wipes?

No next wipe can be predicted for in.high, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 14 days 11 hours.

Lists and tags

What do the server tags on in.high mean?

The game's server browser reads the tags in.high publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; modded (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does in.high appear?

You will find in.high on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto in.high?

You can connect by pressing F1 in Rust and typing client.connect 116.58.190.230:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players 10 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.
modded
Modded Plugins or settings alter the game, so it's 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.