Offline 153.173.2.5:28015 checked 25d ago
Shimeji's Test Server
Connect
srv = rust.server("153.173.2.5: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 bestTop 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 | Sun 4 Oct, 00:35 UTC25d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 153.173.2.5:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 00:35 UTC
- hostname
- –
- first seen
- 3 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 · 149 on average | 168/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 71/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Shimeji's Test Server take in the server rankings?
Player hours over seven days put Shimeji's Test Server at #13,882, in the top 61% of the ranked set.
How full does Shimeji's Test Server run?
Offline now for Shimeji's Test Server, with the last sample 25 days 8 hours ago.
Server facts
What Rust version does Shimeji's Test Server run?
Rust network protocol 2634 and build 166652 on Windows is what Shimeji's Test Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Shimeji's Test Server, and is it up?
Shimeji's Test Server is offline at this refresh; the last response came 25 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 3 October 2026.
Where does Shimeji's Test Server sit?
There is no region published for Shimeji's Test Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 153.173.2.5:28015 is its address.
Map and rules
Which rules apply on Shimeji's Test Server, and what settings?
No gather rate appears in the name: Shimeji's Test Server. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Anti-cheat status: VAC on.
Wipe schedule
On what schedule does Shimeji's Test Server wipe?
The record for Shimeji's Test Server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 25 days 11 hours ago.
On Shimeji's Test Server, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Shimeji's Test Server appear among Rust Data lists and filters?
On Rust Data, Shimeji's Test Server appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Shimeji's Test Server?
Read by the game's server browser, the tags Shimeji's Test Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into Shimeji's Test Server?
The manual route: launch Rust, F1, then client.connect 153.173.2.5:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.