Offline 120.230.26.42:28015 checked 37d ago
.....
Connect
srv = rust.server("120.230.26.42: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 bestWipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Sunday 1 November, 18:41 UTC, in 4d 23h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 4d 23h | Sun 1 Nov, 18:41 UTC | wipe |
| 1 | 8d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 18d 23h | Sun 15 Nov, 18:41 UTC | wipe |
| 3 | 32d 23h | Sun 29 Nov, 18:41 UTC | wipe |
| 4 | 36d 23h | Thu 3 Dec, 19:00 UTC | FW 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 20 Sep, 18:41 UTC37d 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
- 120.230.26.42:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 20 Sep 2026, 19:08 UTC
- hostname
- –
- first seen
- 20 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 | [EU/GER] Rust Norddeutschland PVE | EU · groups of 8+ · biweekly · 18 on average | 21/100 |
| 1 | |US|BunnysBoomBoomRoom|PvE| | NA · groups of 8+ · biweekly · 7 on average | 3/50 |
| 2 | [EU/GER] Der Aussenposten PvE | Vanilla | Beginners Welcome | EU · groups of 8+ · biweekly · 5 on average | 2/75 |
| 3 | 【流星】PVE｜仿官原倍｜休闲养老｜萌新天堂 | EA · groups of 18+ · biweekly · 3 on average | 1/100 |
| 4 | Rumble Bees PvE | Quests | Prestige | MORE | groups of 8+ · biweekly · 2 on average | 3/100 |
| 5 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 243 on average | 239/2000 |
Quick answers
From the figures on this page.
Player counts
How does ..... compare in the rankings?
Player hours over seven days put ..... at #14,440, in the top – of the ranked set.
How full does ..... run?
The current row shows ..... offline; the last response was 37 days ago.
Server data
What is the Rust version on .....?
Rust network protocol 2633 and build 164530 on Windows is what ..... runs. Steam updates your game for you, but the protocol must match to join.
Is ..... up, and what does its uptime show?
Offline now for ....., last seen 37 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 20 September 2026.
In which location is ..... hosted?
No region is published by ...... Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 120.230.26.42:28015.
Settings and map
Which settings and rules does ..... run?
No gather rate appears in the name: ...... Eight players per group: that is the game's default, and it applies here. Recorded as pve, player combat is not allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.
What is the map on .....?
A procedural map runs on ....., generated by the game.
Wipe data
When does ..... wipe, and on what schedule?
The prediction follows the tag, because .....'s wipes on record are too few to confirm the schedule. The schedule puts the next wipe on Sunday 1 November at 18:41 UTC. The world it runs now was generated 37 days ago. A fortnightly wipe schedule is published in its tags.
On ....., what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Tags and filters
Where does ..... appear among Rust Data lists and filters?
These Rust Data lists include .....: Rust community servers, unfiltered and Rust PvE servers. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks.
How should you read the server tags on .....?
Read by the game's server browser, the tags ..... publishes are: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^p (PvE): No player-versus-player combat; the danger comes from the world. 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 .....?
In Rust, F1 opens the console: type client.connect 120.230.26.42:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.