Online 111.228.22.153:28026 checked 9m ago
**/*2634
Connect
srv = rust.server("111.228.22.153:1")
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 bestTop 25% 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, 30 hours in, with 1 in the queue.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 07:02 UTC1d ago | NaN | NaN | running | 1 |
| 1 | Sun 25 Oct, 07:41 UTC2d ago | 2+1 queue | NaN | 1 days | 1 |
| 2 | Sat 24 Oct, 06:30 UTC3d ago | 1 | NaN | 1 days | 1 |
| 3 | Thu 22 Oct, 11:52 UTC5d ago | 1 | NaN | 1.8 days | 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
- 111.228.22.153:28026
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 07:02 UTC
- hostname
- –
- first seen
- 21 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 · 163 on average | 184/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 176/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 29/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 150/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 54/1000 |
Quick answers
From the figures on this page.
Population data
How does **/*2634 compare in the rankings?
Rank #5,602 on seven-day player hours for **/*2634, within the top 25% of all ranked servers.
How full does **/*2634 run?
Point query at this second: **/*2634 returns 0 players. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 2 players.
Server data
What is the Rust version on **/*2634?
The build is Rust network protocol 2634 and build 167781 on Windows, run by **/*2634. Steam updates your game for you, but the protocol must match to join.
Is **/*2634 up, and what does its uptime show?
The current sample puts **/*2634 online. Over the last 5 full days the hours up number 40 of 120, 33%. Rust Data logged it first on 21 October 2026.
In which location is **/*2634 hosted?
For **/*2634, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 111.228.22.153:28026 is its address.
Map and rules
Which settings and rules does **/*2634 run?
The name **/*2634 carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. The VAC field reads off.
What is the map on **/*2634?
**/*2634 runs a procedural map, which the game generates.
Wipe data
On what schedule does **/*2634 wipe?
No next wipe can be predicted for **/*2634, 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. The world it runs now was generated 37 hours ago.
On **/*2634, what happens on wipe day?
The average peak over recent wipes is 1 players. On the latest wipe the peak came 30 hours after the wipe, with a queue of 1.
Tags and filters
Where does **/*2634 appear among Rust Data lists and filters?
These Rust Data lists include **/*2634: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Which meanings do the tags on **/*2634 hold?
These tags are published by **/*2634 and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp0 (Max players): Slot count: 0; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not 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.
How to join
How can I connect to **/*2634?
Enter client.connect 111.228.22.153:28026 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.