Online 116.58.190.230:28015 checked 8m ago
in.high
Connect
srv = rust.server("116.58.190.230:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 11:50 UTC13d ago | 2 | NaN | running | 2 |
| 1 | Fri 2 Oct, 08:15 UTC25d ago | 1 | held half | 12.1 days | 0 |
| 2 | Wed 30 Sep, 13:42 UTC27d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
4000 · seed 814592164
- map
- Procedural Map
- size
- 4000
- seed
- 814592164
Server
srv.info()- address
- 116.58.190.230:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 11:50 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 159 on average | 44/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 53/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 22/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Population data
How does in.high compare in the rankings?
Over the last seven days in.high sits at #4,558 on player hours, in the top 20% of ranked servers.
What population does in.high carry?
The sample now reads 1 players for in.high, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 11:00 UTC is the busiest, at 2 players.
Server data
How well does in.high perform?
Averaged over 48 hours: 133 server fps, never under 103. Buildings, deployables and all else in the world took the count as high as 95,634 entities. Memory peaked at 3,385 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is in.high on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by in.high. The protocol has to match before you can join, and Steam does the updating.
Is in.high up, and what does its uptime show?
Online is the state at the latest refresh for in.high. Count back 5 days from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does in.high sit?
No region is published by in.high. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 116.58.190.230:28015.
Rules, settings, map
Which rules apply on in.high, and what settings?
The name in.high carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on in.high?
The game generates the map on in.high: procedural, size 4,000, seed 814592164. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does in.high wipe, and on what schedule?
No next wipe can be predicted for in.high, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 13 days 16 hours ago, and that is the one in play.
What is wipe day on in.high like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags, lists
Which lists on Rust Data hold in.high, and which filters?
These Rust Data lists include in.high: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on in.high?
Read by the game's server browser, the tags in.high publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into in.high?
The manual route: launch Rust, F1, then client.connect 116.58.190.230:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.