Offline 162.19.159.38:27171 checked 10d ago
RIN EVENT
Connect
srv = rust.server("162.19.159.38:27172")
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 7 Oct. 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 best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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 3, 24 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 7 Oct, 11:38 UTC22d ago | 3 | NaN | running | 0 |
# 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
4500 · seed 1403708994
- map
- Procedural Map
- size
- 4500
- seed
- 1403708994
Server
srv.info()- address
- 162.19.159.38:27171
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 11:59 UTC
- hostname
- –
- first seen
- 7 Oct 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 · 149 on average | 186/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 179/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 91/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 284/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 236/700 |
Quick answers
From the figures on this page.
Population data
How does RIN EVENT compare in the rankings?
Player hours over seven days put RIN EVENT at #15,255, in the top 70% of the ranked set.
What population does RIN EVENT carry?
The current row shows RIN EVENT offline; the last response was 10 days 21 hours ago.
About the server
What is the Rust version on RIN EVENT?
Version Rust network protocol 2634 and build 167781 on Linux is reported by RIN EVENT. Joining needs the same protocol on your game; Steam handles the update.
Is RIN EVENT up, and what does its uptime show?
The latest sample has RIN EVENT offline, with a last sighting 10 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 7 October 2026.
Which location does RIN EVENT run from?
No region is published by RIN EVENT. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 162.19.159.38:27171 is its address.
Rules, settings, map
Which settings and rules does RIN EVENT run?
You will not find a gather rate in the string RIN EVENT. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has RIN EVENT selected?
RIN EVENT runs a procedural map of size 4,500 with seed 1403708994, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does RIN EVENT wipe, and on what schedule?
The record for RIN EVENT holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 22 days 3 hours ago.
On RIN EVENT, what happens on wipe day?
Recent wipes averaged 3 players at their peak. The crowd on the latest wipe topped out 24 hours after it began.
Tags and filters
Which lists on Rust Data hold RIN EVENT, and which filters?
The Rust Data lists that RIN EVENT fits 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.
Which meanings do the tags on RIN EVENT hold?
These tags are published by RIN EVENT and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join RIN EVENT?
In Rust, F1 opens the console: type client.connect 162.19.159.38:27171. Launch Rust on this page does the same by opening the game through Steam and connecting.