in.high
Online 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 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.
- usual gap
- 7 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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 |
|---|---|---|---|---|
14 OCT 2026Wed 14 Oct, 11:50 UTC14d ago |
2 | – | running | 2 |
2 OCT 2026Fri 2 Oct, 08:15 UTC26d ago |
1 | held half | 12.1 days | 0 |
30 SEP 2026Wed 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.
Quick answers
From the figures on this page.
Rules and settings
Where can you read the rules and settings that apply on in.high?
The name of in.high does not state a gather rate. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on in.high?
Size 4,000, seed 814592164: the game generates the procedural map on in.high. You can view the map on RustMaps from this page, as the same size and seed give the same map.
Tags
Where does in.high appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include in.high are Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which tags are attached to in.high, and what do they stand for?
The server's own tags are listed here, and the game's server browser reads them: in.high gives gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): Player cap: 10; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): This one is Modded, since plugins or settings change how it plays; modded (Modded): This one is Modded, since plugins or settings change how it plays. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipes and resets
What should you expect on in.high when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
When does in.high wipe?
There is no next wipe to predict for in.high, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 14 days 7 hours is when its current world was made.
Players and ranking
How is in.high ranked compared with the rest?
Filed under rankings: #4,560 for in.high on seven-day player hours, top 21% overall.
What does the player count on in.high look like?
Filed under live counts: in.high, 0 players on 10 slots at present. The seven-day average is 0 players; the peak reached 2. The busiest point in the last 48 hours was 12:00 UTC, averaging 2 players.
Server facts
Which Rust build is in.high running?
Rust network protocol 2635 and build 168909 on Windows is what you will find on in.high. To join you need the same protocol; Steam handles the update.
How reliable is in.high, and is it online now?
The server is live at this moment: in.high. About 5 days 14 hours ago, by its own uptime figure, is when it last restarted. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. It was first recorded by Rust Server Index on 13 September 2026.
How well does in.high perform?
Averaged over the last 48 hours, server fps was 133, with a low of 103. The entity count reached 95,432, covering buildings, deployables and all else in the world. Up to 3,509 MB of memory was in use. Lag, to players, is low fps and an entity count that climbs.
Which region is in.high in?
No region is published by in.high. Rust Server Index takes the server's word for its location and does not look up the machine's position. You will reach it at 116.58.190.230:28015.
Connecting
What steps lead onto in.high?
If you would rather use the console, press F1 in Rust and enter client.connect 116.58.190.230:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,modded
Game
gmrust
mp10
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.