Server profile
in.high
Online, with 0 of 10 players on; ranked #4,580 of every public Rust server, the top 21%. It last wiped 13d ago.
Online 116.58.190.230:28015 checked 11m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 21% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
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.
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 11:50 UTC13d ago | 2 | – | running | 2 |
| Fri 2 Oct, 08:15 UTC25d ago | 1 | held half | 12.1 days | 0 |
| Wed 30 Sep, 13:42 UTC27d ago | 1 | – | 1.8 days | 1 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
On in.high, what happens on wipe day?
Recent wipes peaked at 1 players on average. 0 hours into the latest wipe, the crowd on the server reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
On what schedule does in.high wipe?
No next wipe can be predicted for in.high, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. This world dates from 13 days 9 hours ago.
About the server
How well does in.high perform?
Server fps averaged 133 over 48 hours; the lowest reading was 117. The world held a peak of 95,852 entities, counting buildings, deployables and all the rest. It drew as much as 3,370 MB of memory. Lag, for players, is low fps and an entity count that keeps climbing.
Which Rust version is in.high on?
Rust network protocol 2635 and build 168909 on Windows is what in.high runs. You can only join if your game is on the same protocol; Steam handles that update.
What does uptime look like for in.high, and is it online?
At the time of this check in.high is online. Going by the uptime figure it gives, its last restart was around 4 days 17 hours ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. On 13 September 2026 is when Rust Insights first saw it.
Where does in.high run from?
A region is not published by in.high. Rust Insights reports the location a server declares, not the physical place of the machine. Connect through 116.58.190.230:28015.
Tags
How should you read the tags listed for in.high?
The tags gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; modded (Modded): The game is changed by plugins or settings, placing it under Modded are what in.high publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
On which Rust Insights lists does in.high appear?
These Rust Insights lists include in.high: Modded Rust servers, explained. You will find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player counts
How many players are on in.high right now, and how does that number move?
Of its 10 slots, in.high currently has 0 filled. The seven-day average is 0 players, and the highest point in that week was 2. The busiest point of the last 48 hours fell at 11:00 UTC, averaging 2 players.
How does in.high compare with other Rust servers in the ranking?
Player hours over seven days put in.high at #4,580, within the top 21% of the ranked field.
Map and rules
How is in.high configured, and what rules apply?
No gather rate appears in the name of in.high. Groups can reach 8 players, which is the default in the game. survival is the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. It is a Modded entry: plugins or settings modify the game. Oxide is the plugin count it runs. Anti-cheat: VAC, from Valve, is on.
What is the map on in.high?
in.high runs a procedural map of size 4,000 with seed 814592164, generated by the game. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.
Connecting
What is the way to join in.high?
Open the console with F1 in Rust and enter client.connect 116.58.190.230:28015. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you.