Open every day, at every hour Admission free 11,601 servers and 32,197 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 4,552Acc. 2026.4552

in.high

Rust server · in the archive since 13 September 2026

Online 116.58.190.230:28015 checked 7m ago

moddedoxide
To visit
Players now 1/ 10
10% full
7-day average0peak 2
Rank#4,552top 20%
Last wipe13d agoWed 14 Oct, 11:50 UTC · no schedule published
Next wipe–no rhythm it keeps

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 28 Oct 2026, 05:10 UTCAll times UTC.

The record of each wipe

  1. Wed 14 Oct 202611:50 UTC13d ago
    Peak
    2
    Crowd
    –
    Lasted
    running
    Players before
    2
  2. Fri 2 Oct 202608:15 UTC25d ago
    Peak
    1
    Crowd
    held half
    Lasted
    12.1 days
    Players before
    0
  3. Wed 30 Sep 202613:42 UTC27d ago
    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.

The rhythm

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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
00.511.5206:0015:0000:0009:0018:0003:00

Hourly average and peak, UTC.

Folder 2

Server performance

05010015020006:0015:0000:0009:0018:0003: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.

Folder 3

Rank

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.

Related exhibits

Similar servers

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

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags and filters

What do the server tags on in.high mean?

The game's server browser reads these tags published by in.high: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings; modded (Modded): Under Modded: the game is changed by plugins or settings. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

Which Rust Server History lists and filters include in.high?

The Rust Server History lists that feature in.high are: Modded Rust servers: the record. It appears under these filters 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.

Server record

Does in.high run smoothly?

Averaged over the last 48 hours: 133 server fps, with 103 the lowest. Buildings, deployables and everything else in the world came to as many as 95,634 entities. Memory use peaked at 3,385 MB. Players feel lag when fps drop and the entity count climbs.

Which version of Rust does in.high run?

The recorded build for in.high is Rust network protocol 2635 and build 168909 on Windows. The protocol must match to join, and Steam handles that update.

Is in.high online, and how reliable is it?

At this moment in.high is online. About 5 days 1 hours ago is when it last restarted, judged by the uptime it reports. It was up for 168 of 168 hours in the last 7 full days, 100% of the time. The first sighting by Rust Server History was on 13 September 2026.

Where is in.high located?

You will find no region published by in.high. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. You can reach it at 116.58.190.230:28015.

Wipe record

What does wipe day look like on in.high?

An average peak of 1 players was drawn by its recent wipes. On the latest wipe, 0 hours after the wipe, the crowd peaked. Above half that peak until the next wipe it stayed in 100% of its recent wipes.

What is the wipe schedule on in.high?

There is no next wipe to predict on in.high, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. 13 days 17 hours ago its current world was made.

Population

How does in.high rank against other Rust servers?

Over seven days of player hours, in.high ranks #4,552, inside the top 20% of all ranked servers.

How busy is in.high?

Against 10 slots, in.high records 1 players right now. The seven-day average stands at 0 players; the peak is 2. The busiest hour of the last 48 was 11:00 UTC, averaging 2 players.

Rules and settings

What are the rules and settings on in.high?

The name of in.high carries no gather rate. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gather, build, raid: the standard game. You may fight and raid other players. Under Modded in the server browser, the game is changed by plugins or settings. The plugin count is Oxide. VAC from Valve is switched on.

Which map does in.high run?

A procedural map of size 4,000 with seed 814592164 is what in.high runs, generated by the game. One size and seed produce one map, which RustMaps can show you from this page.

How to join

How do I join in.high?

Press F1 in Rust to open the console, then enter client.connect 116.58.190.230:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The default cap of 8 per team applies here.
v2635
Protocol To join, your game has to be on protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Networking runs on RakNet, the game's standard layer.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.
modded
Modded Under Modded: the game is changed by plugins or settings.

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.