Skip to the coverage
Live Rust server stats, updated every five minutes.
Rust Live Stats
Live
48,364 players on Rust servers right now 11,659 servers online 3,165 with players on 117 fresh wipes in the last three hours in.high: 1 players on now Updated every five minutes

LiveLive coverage · Rust server

in.high

Key points

  • 1 of 10 players are on now, 10% full.
  • Over the last seven days it averages 0 players, with a peak of 2.
  • It ranks #4,578, the top 21% of all ranked servers.
  • The current map has been up 14d 21h, since Wednesday 14 October, 11:50 UTC.
Join
moddedoxide

Live coverage

newest first · every post is a reading of this server

Now: 1 of 10 players

1/ 10players now 10% full
07-day averagepeak 2
#4,578ranktop 21%
14d agolast wipeno schedule published
–next wipeno rhythm it keeps

Players on in.high

Players

AveragePeak
00.511.5210:0019:0004:0012:0022:0007:00

Hourly average and peak, UTC.

How the server is running

Server performance

05010015020010:0019:0004:0012:0022:0007: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.

Rank #4,578 today

Rank

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

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

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.

7 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
100%crowd heldof 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.

Wipes

newest first

Wipe peaks at 2 players

Peak
2
Crowd
–
Lasted
running
Players before
2

Wipe peaks at 1 player

Peak
1
Crowd
held half
Lasted
12.1 days
Players before
0

Wipe peaks at 1 player

Peak
1
Crowd
–
Lasted
1.8 days
Players before
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
ShockRust | Blue | NoLimit
no group limit · 149 on average
109 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
129 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 118 on average
167 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 93 on average
50 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 88 on average
3 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
25 / 1000

Quick answers

from the figures on this page

Wipe days

What happens on wipe day at in.high?

At their busiest, its recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 100% of its recent wipes.

On what timetable does in.high wipe?

No next wipe can be predicted for in.high, which wipes at irregular times. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 14 days 21 hours.

Lists and tags

Where does in.high appear in Rust Live Stats lists and filters?

On Rust Live Stats, in.high is listed under Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the tags on in.high?

gmrust (Game mode): Survival here follows standard Rust; mp10 (Max players): The slot count is 10; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game changes here through plugins or settings, so it is Modded; modded (Modded): The game changes here through plugins or settings, so it is Modded: that is the tag list in.high publishes for the game's server browser. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.

Player numbers

How full is in.high at the moment?

1 of in.high's 10 slots are filled right now. The seven-day average is 0 players, with a peak of 2. The busiest hour in the past 48 was 12:00 UTC, averaging 2 players.

Where does in.high sit in the server rankings?

Ranked by seven-day player hours, in.high is #4,578, placing it in the top 21% of ranked servers.

Settings and map

What settings and rules does in.high run?

Nothing in the name of in.high states a gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.

Which map is live on in.high?

Size 4,000, seed 814592164: that is the procedural map the game generates for in.high. Same size, same seed, same map: RustMaps has it, reachable from this page.

About the server

Where does in.high sit geographically?

No region is published by in.high. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 116.58.190.230:28015.

Is performance on in.high steady?

It never went below 103 server fps in the last 48 hours, averaging 132. Buildings, deployables and everything else in the world added up to a maximum of 95,629 entities. Memory use peaked at 3,559 MB. A climbing entity count and low fps are felt as lag by players.

What version of Rust is running on in.high?

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

Is in.high up now, and how steady is its uptime?

in.high is up and running at this moment. Based on the uptime it reports, the last restart was about 6 days 5 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. The first sighting by Rust Live Stats was on 13 September 2026.

Connecting

What steps connect you to in.high?

Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 116.58.190.230:28015.

Server tags

what each one means

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

Game

gmrust
Game mode Survival here follows standard Rust.
mp10
Max players The slot count is 10.
ts8
Group limit 8 per team at most, the game's default setting.
v2635
Protocol The server runs protocol 2635, so match that version to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer — the game's standard one.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, runs on this server.
^z
Modded The game changes here through plugins or settings, so it is Modded.
modded
Modded The game changes here through plugins or settings, so it is 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.