Local forecast
in.high
Online 116.58.190.230:28015 checked 9m ago
Current conditions
observed 9m agoplayers now
0% full
- 7-day average
- 0
- peak 2
- Rank
- #4,503
- top 20%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
Next wipe
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 12:50 UKWed 14 Oct, 11:50 UTC · 15d ago | 2 | – | running | 2 |
| Fri 2 Oct, 09:15 UKFri 2 Oct, 08:15 UTC · 27d ago | 1 | held half | 12.1 days | 0 |
| Wed 30 Sep, 14:42 UKWed 30 Sep, 13:42 UTC · 29d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
Does in.high hold a steady performance?
Its average over the last 48 hours was 133 server fps, and it never dropped below 103. Buildings, deployables and all else in the world took the entity count to a peak of 95,629. The peak memory draw was 3,738 MB. Players feel lag when fps drops and the entity count climbs.
Is in.high online at the moment, and how consistent is its uptime?
You will find in.high online at the moment. The uptime it reports puts the last restart about 6 days 12 hours ago. It was up for 167 of 168 hours across the last 7 full days, 99% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
In which location does in.high sit?
For in.high, no region is published. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 116.58.190.230:28015 is its address.
What Rust version is in.high on?
Rust network protocol 2635 and build 168909 on Windows is what in.high runs. To join you need the same protocol, and Steam handles the update.
Lists and tags
Which meaning sits behind each tag on in.high?
These are the tags in.high publishes for the game's server browser to read: gmrust (Game mode): Standard survival, the Rust way; mp10 (Max players): Capacity: 10; ts8 (Group limit): Teams are at the game default of 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): This server carries no region code; ^o (Oxide): Oxide, known too as uMod, provides the plugin framework; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded; modded (Modded): Plugins or settings alter the game here, so it is listed under Modded. At the top of this page you can see the player count now, the queue and the world's creation time, all from the tags.
Which Rust Wipe Stats filters and lists carry in.high?
The Rust Wipe Stats lists that include in.high are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Settings and rules
Which map is in use on in.high?
The game generates the map on in.high, procedural, size 4,000, seed 814592164. The same map comes from the same size and seed, and RustMaps shows it from this page.
What settings does in.high use, and what rules does it enforce?
The name of in.high says nothing about gather rate. No group setting is published, so the game default of 8 players applies. survival is the game mode, the usual game of gathering, building and raiding. Raiding and player combat are both allowed. Plugins or settings change the game here, and the browser files it under Modded. Plugin frameworks in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe times
On what schedule does in.high wipe?
No next wipe can be predicted for in.high: it wipes at irregular times. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. 15 days 3 hours is how long the current world has been running.
What happens on in.high when wipe day arrives?
The average peak across its recent wipes was 1 players. Peak numbers on the latest wipe arrived 0 hours after the reset. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
Population
Is in.high busy or quiet?
The live count for in.high: 0 players, with 10 slots in total. Across the past week it peaked at 2 and averaged 0 players. The last 48 hours peak at 12:00 UTC, when the average was 2 players.
How does in.high compare with other Rust servers in the rankings?
Player hours over the past week put in.high at #4,503, inside the top 20% of all ranked servers.
Join the server
What do you do to join in.high?
Open the console in Rust with F1, then type client.connect 116.58.190.230:28015 to join. On this page, Launch Rust does the same through Steam.