Online 46.62.164.38:26069 checked 7m ago
Shivazerg Solo *Whitelist only*
Connect
srv = rust.server("46.62.164.38:28017")
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. 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 35% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 22:01 UTC3d ago | 1 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 46.62.164.38:26069
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 22:01 UTC
- hostname
- –
- first seen
- 24 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 237/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 162/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 292 on average | 28/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 291 on average | 16/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 34/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 45/200 |
Quick answers
From the figures on this page.
Population
What position does Shivazerg Solo *Whitelist only* take in the server rankings?
Player hours over seven days put Shivazerg Solo *Whitelist only* at #7,682, in the top 35% of the ranked set.
How many players does Shivazerg Solo *Whitelist only* hold at once?
The sample now reads 0 players for Shivazerg Solo *Whitelist only*, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 22:00 UTC is the busiest, at 1 players.
Server facts
Which Rust version is Shivazerg Solo *Whitelist only* on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Shivazerg Solo *Whitelist only*. Steam updates your game for you, but the protocol must match to join.
How reliable is Shivazerg Solo *Whitelist only*, and is it up?
Online is the state at the latest refresh for Shivazerg Solo *Whitelist only*. Over the last 4 full days the hours up number 50 of 96, 52%. Rust Data logged it first on 24 October 2026.
Which location does Shivazerg Solo *Whitelist only* run from?
There is no region published for Shivazerg Solo *Whitelist only*. Rust Data does not look up where the machine stands; it shows where a server says it is. 46.62.164.38:26069 is its address.
Map and rules
Which rules apply on Shivazerg Solo *Whitelist only*, and what settings?
No gather rate appears in the name: Shivazerg Solo *Whitelist only*. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
Which map has Shivazerg Solo *Whitelist only* selected?
A procedural map runs on Shivazerg Solo *Whitelist only*, generated by the game.
Wipe schedule
On what schedule does Shivazerg Solo *Whitelist only* wipe?
The record for Shivazerg Solo *Whitelist only* holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 2 hours ago.
On Shivazerg Solo *Whitelist only*, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.
Tags, lists
Which lists on Rust Data hold Shivazerg Solo *Whitelist only*, and which filters?
On Rust Data, Shivazerg Solo *Whitelist only* appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Shivazerg Solo *Whitelist only*?
Read by the game's server browser, the tags Shivazerg Solo *Whitelist only* publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Shivazerg Solo *Whitelist only*?
In Rust, F1 opens the console: type client.connect 46.62.164.38:26069. Launch Rust on this page does the same by opening the game through Steam and connecting.