Rust StatisticsWorking papers on every public Rust server · 67,519 players now

in.high

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 15m ago · 116.58.190.230:28015

Abstract

We describe the public Rust server in.high, reached at 116.58.190.230:28015. At the last check it held 2 of 10 places, against a seven-day mean of 0 and a peak of 21. It ranks #4,650 of all servers, the top 21%. It last wiped 14d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now2/1020% full
In the queue0no queue
Seven-day mean0peak 2, 48 h peak 1
Rank2#4,650top 21%
Last wipe14d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75113:0022:0007:0016:0001:0010:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020013:0022:0007:0016:0001:0010:00
Figure 2: 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.

4Rank

The server stands in the top 21% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap7 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak1players, last three wipes
Crowd held100%of its cycles kept half the crowd
Wed 14 OctFri 2 OctWed 30 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 14 Oct, 11:5014d ago 2 – running 2
Fri 2 Oct, 08:1526d ago 1 held half 12.1 d 0
Wed 30 Sep, 13:4227d ago 1 – 1.8 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of in.high
Figure 5: The map: Procedural Map, size 4000, seed 814592164. Open on RustMaps.
Table 4: The server's published settings.
Address116.58.190.230:28015
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe14 Oct 2026, 11:50 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4000
Seed814592164

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 155 on average170/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average132/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average177/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average138/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average14/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does in.high perform well?

Its average server fps over the last 48 hours was 133, with a minimum of 103. Its entity count reached a maximum of 95,519, including buildings, deployables and all other world objects. Memory use peaked at 3,385 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of in.high?

There is no region published for in.high. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 116.58.190.230:28015 is its address.

A.3What is the reliability of in.high, and is it online?

in.high is online at this time. The uptime it reports indicates a restart about 5 days 8 hours ago. The server was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on in.high?

in.high is running Rust network protocol 2635 and build 168909 on the Windows operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5What schedule does in.high follow for wipes?

Prediction of the next wipe is impossible for in.high, which wipes irregularly. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 14 days.

A.6How would you describe wipe day on in.high?

The average busiest point of recent wipes was 1 players. The crowd reached its maximum 0 hours after the latest wipe. For 100% of recent wipes, the population did not fall below half the peak before the next wipe.

Player count

A.7What position does in.high occupy in the ranking of Rust servers?

Ranked by player hours across seven days, in.high holds #4,650, in the top 21% of all ranked servers.

A.8What is the population level of in.high?

The current population of in.high is 2, drawn from 10 slots. Over the last week the count averages 0 players and reaches 2 at its height. Of the last 48 hours, the peak hour falls at 13:00 UTC, with an average of 1 players.

Tags and filters

A.9How should the tags on in.high be interpreted?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): It offers 10 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; modded (Modded): The game is altered by plugins or settings, so it is listed as Modded, which in.high publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can in.high be found among the Rust Statistics lists and filters?

These Rust Statistics lists include in.high: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11What are the settings and rules that govern in.high?

The name of in.high states no gather rate. The group cap is 8 players, which is the default in the game. survival is the game mode here; gather, build and raid: the standard game. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on in.high?

Generated by the game from seed 814592164, the procedural map on in.high measures 4,000. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

How to join

A.13What steps are required to join in.high?

Press F1 inside Rust to open the console and enter client.connect 116.58.190.230:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,modded.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp10Max players. It offers 10 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. This server runs game build 168909.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
moddedModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.