in.high
Online 116.58.190.230:28015 checked 13m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 21% 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 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 163 on average | 31 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 56 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 45 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 8 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14 / 1000 |
Quick answers
from the figures on this pageWipe data
When does in.high wipe?
With irregular wipe times, in.high offers no next wipe to predict. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 13 days 12 hours ago the current world was made.
Wipe day on in.high: what should you expect?
Across recent wipes the busiest point averaged 1 players. Peak population for the latest wipe came 0 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server
Which location hosts in.high?
A region is not published by in.high. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 116.58.190.230:28015 is its address.
What Rust build does in.high run?
Rust network protocol 2635 and build 168909 on Windows is the setup for in.high. Your game must match the protocol to join, and Steam applies that update.
What uptime does in.high show, and is it up?
As of the latest refresh, in.high is online. The uptime it reports puts the last restart at about 4 days 21 hours ago. Uptime over the last full days (7) was 86%, or 144 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
What performance does in.high show?
The 48-hour average was 134 server fps; the low was 117. Buildings, deployables and all other world objects brought the entity total to 95,852. Memory use reached 3,385 MB at peak. Players experience lag as low fps combined with a rising entity count.
Lists and tags
What do in.high's tags stand for?
gmrust (Game mode): Rust survival, standard ruleset; mp10 (Max players): Capacity of 10 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing, where plugins or settings change the game; modded (Modded): Modded listing, where plugins or settings change the game are the tags in.high publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does in.high appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count in.high among their servers: Modded Rust servers: live data. These filters bring it up 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.
Population
Against other Rust servers, how does in.high compare?
On player hours over seven days, in.high ranks #4,581, within the top 21% of ranked servers.
At what level does in.high run its population?
Of 10 slots, 0 are filled on in.high at this refresh. The seven-day mean is 0 players, against a peak of 2. Averaged over 48 hours, activity is highest at 11:00 UTC with 2 players.
Map and rules
What settings and rules does in.high use?
Gather rate is not mentioned in the name of in.high. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.
What is the map for in.high?
The game generates a procedural map of size 4,000 with seed 814592164 for in.high. The map is reproducible from its size and seed and can be seen on RustMaps from here.
How to join
How can a player join in.high?
In the Rust console (F1), enter client.connect 116.58.190.230:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.