in.high
Online 116.58.190.230:28015 checked 10m ago
Measurements
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 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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 wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
| 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 |
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.
Quick answers
Population
How does in.high rank against other Rust servers?
Over the past week it ranks #4,581 for player hours, which puts in.high in the top 21% of all ranked servers.
How busy is in.high?
Of its 10 slots, in.high is using 0 right now. Seven days of counting give an average of 0 players and a peak of 2. Look at the last 48 hours and 11:00 UTC stands out: it averaged 2 players.
Lists and tags
What do the server tags on in.high mean?
The game's server browser reads the tags in.high publishes: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; modded (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include in.high?
These Rust Population lists include in.high: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Wipe notes
What does wipe day look like on in.high?
Across its recent wipes the busiest crowds averaged 1 players. The crowd on the latest wipe peaked 0 hours in. In 100% of recent wipes, half the peak was held until the next wipe.
What is the wipe schedule on in.high?
Irregular times are when in.high wipes, which leaves no next wipe to predict. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 13 days 12 hours ago, that is how long the current world has stood.
Map and rules
Which map does in.high run?
in.high uses a map the game generates, procedural, at size 4,000 with seed 814592164. The map follows from its size and seed, and RustMaps shows it from this page.
What are the rules and settings on in.high?
The name tells you nothing about gather rates: in.high states none. Eight players per group is the default, and it applies here. You get survival here, raid, build and gather: the standard game. You can raid and fight other players here. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. You play with Valve's anti-cheat on: VAC.
About the server
Which version of Rust does in.high run?
The setup is Rust network protocol 2635 and build 168909 on Windows for in.high. Steam updates your game automatically, but you need the same protocol to join.
Does in.high run smoothly?
The last 48 hours saw an average of 134 server fps, with 117 as the lowest. Entities peaked at 95,852, including buildings, deployables and everything else. The highest memory usage was 3,385 MB. What players experience as lag comes from low fps and a rising entity count.
Is in.high online, and how reliable is it?
in.high is up and running at the moment. The uptime it reports suggests a restart roughly 4 days 21 hours ago. It was up 86% of the time over the last 7 full days, 144 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.
Where is in.high located?
Nothing published by in.high states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 116.58.190.230:28015.
Getting in
How do I join in.high?
To connect directly, open Rust's console with F1 and type client.connect 116.58.190.230:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.