in.high
Online 116.58.190.230:28015 checked 8m ago
Server instruments
last reading Wed 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 103 · below 20 is lag, below 10 is badEntities
48 h range 92,959–95,432 · memory 3,299 MBUptime
5 days 19 hours since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 11:50 UTC14d ago | 2 | – | running | 2 |
| Fri 2 Oct, 08:15 UTC26d ago | 1 | held half | 12.1 days | 0 |
| Wed 30 Sep, 13:42 UTC28d 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
the same kind of game, then region, group limit, rate and wipes- 56/500
- 129/100
- 54/225
- 53/700
- 16/200
- 9/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on in.high?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.
How often does in.high wipe, and when?
No next wipe can be predicted for in.high, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 14 days 11 hours ago.
Lists and filters
How should you read the tags on in.high?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; modded (Modded): Modded: plugins or settings depart from the stock game from in.high. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show in.high?
On Rust Metrics, in.high sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does in.high hold among Rust servers?
Ranking for in.high: #4,551 on seven-day player hours, top 20% of all ranked servers.
What is the population on in.high?
0 of 10 slots are filled on in.high right now. Seven-day check: 0 players on average. Peak reading: 2. The last 48 hours peaked at 12:00 UTC, averaging 2 players at that hour.
Server details
What location is in.high hosted in?
No region comes from in.high. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 116.58.190.230:28015.
What Rust version is in.high on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by in.high. To get in, your game needs the same protocol; Steam applies the update.
How does in.high perform?
Over the last 48 hours the average was 133 server fps; the floor was 103. Reading: 95,432 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 3,509 MB. Expect lag when fps falls and entities climb.
Is in.high up, and how often does it stay up?
Check: connection. in.high is online at this moment. By its reported uptime, the last restart was roughly 5 days 19 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What settings and rules apply on in.high?
Reading the name gives no gather rate for in.high. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on in.high?
From seed 814592164, the game generates the procedural map on in.high. Its size is 4,000. The map repeats when size and seed match. Open it on RustMaps from this page.
How to join
How can you get onto in.high?
To join: start Rust, press F1 and type client.connect 116.58.190.230:28015. Or press Launch Rust here and Steam opens the game and connects you.