Offline 64.26.46.102:28015 checked 6d ago
VibeRust | Whitelisted only
Connect
srv = rust.server("64.26.46.102: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. 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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 00:42 UTC14d ago | 0 | 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
- 64.26.46.102:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 00:42 UTC
- hostname
- –
- first seen
- 27 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does VibeRust | Whitelisted only rank?
Over the last seven days VibeRust | Whitelisted only sits at #15,373 on player hours, in the top 69% of ranked servers.
How full does VibeRust | Whitelisted only run?
Offline now for VibeRust | Whitelisted only, with the last sample 6 days 8 hours ago. Over the last seven days it averaged 0 players.
Server data
Which Rust version is VibeRust | Whitelisted only on?
Rust network protocol 2634 and build 167781 on Windows is what VibeRust | Whitelisted only runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is VibeRust | Whitelisted only, and is it online now?
VibeRust | Whitelisted only is offline at this refresh; the last response came 6 days 8 hours ago. 36 of 168 hours up over the last 7 full days, or 21%. Its earliest recorded date in Rust Data is 27 September 2026.
Where does VibeRust | Whitelisted only sit?
No region is published by VibeRust | Whitelisted only. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 64.26.46.102:28015 is its address.
Settings and map
Which settings and rules does VibeRust | Whitelisted only run?
The name VibeRust | Whitelisted only 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. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has VibeRust | Whitelisted only selected?
The game generates its map: procedural, on VibeRust | Whitelisted only.
Wipe data
When does VibeRust | Whitelisted only wipe, and how often?
The record for VibeRust | Whitelisted 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. A new world was started 14 days 18 hours ago, and that is the one in play.
On VibeRust | Whitelisted only, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold VibeRust | Whitelisted only, and which filters?
These Rust Data lists include VibeRust | Whitelisted only: 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.
How should you read the server tags on VibeRust | Whitelisted only?
The game's server browser reads these tags from VibeRust | Whitelisted only: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; 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): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join VibeRust | Whitelisted only?
In Rust, F1 opens the console: type client.connect 64.26.46.102:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.