Skip to the page
Network live 11,802 servers online 77,039 players aboard 111 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

in.high

Online 116.58.190.230:28015 checked 7m ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 14d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 10 players now 0% full
07-day averagepeak 2
#4,545ranktop 21%
14d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
00.511.5221:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

05010015020021:0006:0015:0000:0009:0019: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

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 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

every wipe as a delivery, newest first
  1. Wed 14 Oct, 11:50 UTC 12:50 UK · 14d ago
    Wipe delivered
    Peak
    2
    Crowd
    –
    Lasted
    running
    Players before
    2
  2. Fri 2 Oct, 08:15 UTC 09:15 UK · 26d ago
    Wipe delivered
    Peak
    1
    Crowd
    held half
    Lasted
    12.1 days
    Players before
    0
  3. Wed 30 Sep, 13:42 UTC 14:42 UK · 28d ago
    Wipe delivered
    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 parcels

Similar servers

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

  1. ShockRust | Blue | NoLimitno group limit · 157 on average 119 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average 121 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average 140 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average 105 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average 31 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average 30 / 1000
Help desk

Quick answers

From the figures on this page.

Player activity

Where does in.high place among Rust servers?

In the top 21% of all ranked servers sits in.high, at #4,545 on hours played over seven days.

How many players are on in.high right now?

At the moment 0 players are on in.high, which has 10 slots. Averaged over the past week: 0 players, peaking at 2. The busiest hour over the last 48 hours was 12:00 UTC, averaging 2 players.

Rules and settings

On what map does in.high take place?

Size 4,000 and seed 814592164 define the procedural map in.high runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What are the rules on in.high, and what settings does it run?

The name of in.high gives no gather rate. Up to 8 players can join a group, the default for the game. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Plugins come from Oxide. The VAC anti-cheat from Valve is enabled.

About the server

In which region is in.high based?

No region is published by in.high. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 116.58.190.230:28015 is its address.

Does in.high perform well?

The 48-hour average for server fps stands at 133, never dipping below 103. Buildings, deployables and all the rest of the world pushed its entity count as high as 95,432. The highest memory reading was 3,509 MB. Lag, to players, means low fps alongside an entity count on the rise.

How reliable is in.high, and is it currently online?

You can find in.high online at present. The uptime it reports puts its last restart at about 5 days 14 hours ago. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.

What Rust version is in.high using?

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

Wipe schedule

How does in.high handle its wipe days?

The average busiest point of its recent wipes was 1 players. On the latest wipe, 0 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

On what schedule does in.high reset its map?

There is no next wipe to predict for in.high: it wipes at irregular times. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. You are playing a world created 14 days 9 hours.

Server tags

Where does in.high appear in Rust Wipe Tracker lists and filters?

You will find in.high on the following Rust Wipe Tracker lists: Modded Rust servers. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What is the meaning of the server tags on in.high?

The game's server browser picks up these in.high tags: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): It holds 10 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; modded (Modded): The game is changed by plugins or settings, hence the Modded listing. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Connecting

How do you connect to in.high?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter 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 in standard Rust.
mp10
Max players It holds 10 slots.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code A region code isn't set.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.
modded
Modded The game is changed by plugins or settings, hence the Modded listing.

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.