Offline 178.173.248.141:27000 checked 34d ago
SychkaRust
Connect
srv = rust.server("178.173.248.141:27001")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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, measured since 24 Sep. 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 40% 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 8, 9 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 18:00 UTC35d ago | 8 | NaN | running | 0 |
| 1 | Thu 24 Sep, 11:50 UTC35d ago | 8 | NaN | 0.3 days | 0 |
| 2 | Thu 24 Sep, 05:06 UTC35d ago | 8 | NaN | 0.3 days | 1 |
# 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
3000 · seed 418856- map
- Procedural Map
- size
- 3000
- seed
- 418856
Server
srv.info()- address
- 178.173.248.141:27000
- region
- –
- max players
- 200
- group limit
- not published
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 22:59 UTC
- hostname
- –
- first seen
- 24 Sep 2026
About this server · in its own words
print(srv.description)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 · 151 on average | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 196/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 73/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 211/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
How does SychkaRust compare in the rankings?
Player hours over seven days put SychkaRust at #9,072, in the top 40% of the ranked set.
How full does SychkaRust run?
The current row shows SychkaRust offline; the last response was 34 days 13 hours ago.
Server facts
What is the Rust version on SychkaRust?
Version Rust network protocol 2633 and build 163794 on Linux is reported by SychkaRust. Steam updates your game for you, but the protocol must match to join.
How reliable is SychkaRust, and is it up?
SychkaRust is offline at this refresh; the last response came 34 days 13 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 24 September 2026.
Where does SychkaRust sit?
For SychkaRust, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 178.173.248.141:27000 is its address.
Map and rules
Which settings and rules does SychkaRust run?
You will not find a gather rate in the string SychkaRust. The field for group size is empty. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. VAC is running: Valve's anti-cheat is on.
Which map has SychkaRust selected?
SychkaRust runs a procedural map of size 3,000 with seed 418856, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
On what schedule does SychkaRust wipe?
SychkaRust wipes on no fixed rhythm, so there is nothing to predict. 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 34 days 20 hours ago.
On SychkaRust, what happens on wipe day?
Recent wipes averaged 8 players at their peak. The crowd on the latest wipe topped out 9 hours after it began.
Lists and tags
Which Rust Data filters and lists contain SychkaRust?
The Rust Data lists that SychkaRust fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z.
How should you read the server tags on SychkaRust?
The game's server browser reads these tags from SychkaRust: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): The server lists 200 slots; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; ^z (Modded): Modded listing: the game is changed by plugins or settings; h7af5fc78 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; stok (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. 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 SychkaRust?
Enter client.connect 178.173.248.141:27000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://anti-rust.gamestores.ru/#/app/store/ is the website recorded for it.