Offline 102.135.145.218:28015 checked 35d ago
My Rust Server_test
Connect
srv = rust.server("102.135.145.218: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 61% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 23 Sep, 13:10 UTC35d 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
- 102.135.145.218:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Sep 2026, 13:10 UTC
- hostname
- –
- first seen
- 23 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 555 on average | 164/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 96/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 15/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 286 on average | 17/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 12/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 17/200 |
Quick answers
From the figures on this page.
Population
How does My Rust Server_test compare in the rankings?
Over the last seven days My Rust Server_test sits at #13,182 on player hours, in the top 61% of ranked servers.
How full does My Rust Server_test run?
The current row shows My Rust Server_test offline; the last response was 35 days 12 hours ago.
About the server
What Rust version does My Rust Server_test run?
The build is Rust network protocol 2633 and build 165217 on Windows, run by My Rust Server_test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is My Rust Server_test, and is it online now?
My Rust Server_test is offline at this refresh; the last response came 35 days 12 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 23 September 2026.
Which location does My Rust Server_test run from?
There is no region published for My Rust Server_test. 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 102.135.145.218:28015.
Settings and map
What rules and settings are recorded for My Rust Server_test?
You will not find a gather rate in the string My Rust Server_test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has My Rust Server_test selected?
The game generates its map: procedural, on My Rust Server_test.
Wipes and dates
On what schedule does My Rust Server_test wipe?
A rhythm cannot be read from the wipes of My Rust Server_test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 35 days 13 hours ago.
On My Rust Server_test, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold My Rust Server_test, and which filters?
These Rust Data lists include My Rust Server_test: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on My Rust Server_test?
Read by the game's server browser, the tags My Rust Server_test publishes are: gmvanilla (Game mode): Survival in vanilla form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Build number: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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.
Connecting
How can I connect to My Rust Server_test?
The manual route: launch Rust, F1, then client.connect 102.135.145.218:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.