in.high
116.58.190.230:28015 checked 2h ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1.8 days between real wipes
- wipe-day peak
- 1 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 08:15 UTC 11d ago | 1 | – | running | 0 |
| Wed 30 Sep, 13:42 UTC 13d 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
Quick answers
Population
Where does in.high sit in the rankings?
Rank #4,480 over the last seven days in player hours: in.high, inside the top 20% of ranked servers.
Is in.high busy?
At this moment, in.high is offline, with the last sighting 2 hours ago. Averaged across the last seven days: 0 players, peaking at 2. In the last 48 hours, 12:00 UTC saw the highest activity, with an average of 2 players.
Tags and Filters
What is the meaning of the tags on in.high?
Read by the game's server browser, the tags in.high publishes are: gmrust (Game mode): Survival as standard in Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs166586 (Build): Running build 166586; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): No region code listed; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it appears under Modded; modded (Modded): Plugins or settings alter the game, so it appears under Modded. At the top of this page you also see its players now, its queue and when its world was made, taken from the tags.
Which lists and filters on BestRustServers.xyz contain in.high?
The BestRustServers.xyz lists that include in.high are: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server Overview
in.high Rust version: which one?
The combination is Rust network protocol 2634 and build 166586 on Windows for in.high. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on in.high smooth?
Its average server fps over the last 48 hours was 195, with a low of 67. It held up to 75,927 entities: everything from buildings to deployables in the world. At its highest, memory usage was 2,586 MB. A climbing entity count and low fps are felt by players as lag.
in.high uptime and reliability: what are they?
Offline now for in.high, last seen 2 hours ago. About 15 hours ago is when it last restarted, based on its uptime. It was up 99% of the time over the last 7 full days, 166 of 168 hours. On 13 September 2026, BestRustServers.xyz saw it for the first time.
in.high location: where is it?
There is no region published by in.high. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. You can reach it at 116.58.190.230:28015.
Rules and Settings
Which map is used on in.high?
Generated by the game, the map on in.high is procedural, size 3,200, seed 123456. The map can be viewed on RustMaps from this page, since size and seed fix it.
What are the settings and rules for in.high?
The name in.high carries no gather multiplier. No group limit is stated; the game's default of 8 players applies. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. The Modded section of the browser holds it: plugins or settings apply. Plugins in use: Oxide. The server has VAC on.
Wipe Cycle
On what schedule does in.high wipe?
in.high's wipe rhythm cannot be told from the wipes on record, which are too few. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. Its world dates from 9 days 21 hours.
On in.high, what occurs on wipe day?
An average peak of 1 players was drawn by its recent wipes. 0 hours after the latest wipe, the crowd hit its peak.
Connect
in.high joining: how is it done?
Use the F1 console: client.connect 116.58.190.230:28015. Launch Rust on this page does the same by opening Rust through Steam and connecting.
Server tags
Published as mp10,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z,modded
Game
gmrust- Game mode Survival as standard in Rust.
mp10- Max players Slots: 10.
ts8- Group limit Default team size: 8.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs166586- Build Running build 166586.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code No region code listed.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
^z- Modded Plugins or settings alter the game, so it appears under Modded.
modded- Modded Plugins or settings alter the game, so it appears 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.