Station XX-8973 · no signal
SychkaRust1
Offline 178.173.248.141:27002 checked 34d ago
- Players now
- 8/ 200
- 4% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #8,973
- top 40%
- Last wipe
- 34d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 8of 200 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.3 daysbetween real wipes
- wipe-day peak
- 8players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 8, 5 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 24 Sep, 22:00 UTC34d ago | M0.9▲rising | 8 | – | running | 0 | |
| Thu 24 Sep, 14:27 UTC34d ago | M0.9▲rising | 8 | – | 0.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on SychkaRust1?
SychkaRust1 runs a procedural map of size 3,000 with seed 233782, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on SychkaRust1?
You will find no gather rate in the name of SychkaRust1. It gives no group limit in its listing. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on SychkaRust1 right now?
SychkaRust1 is not responding at this moment and is offline, last seen 34 days 6 hours ago.
How does SychkaRust1 rank against other Rust servers?
On player hours for the past week, SychkaRust1 sits at #8,973, which puts it inside the top 40% of every ranked server.
Server details
How reliably does SychkaRust1 stay online?
As recorded now, SychkaRust1 is not reachable, the last contact having been 34 days 6 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 24 September 2026 is when Rust Server Trends first recorded it.
Which region does SychkaRust1 run from?
Nothing about a region comes from SychkaRust1. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 178.173.248.141:27002 is the address it uses.
What build of Rust does SychkaRust1 use?
On Linux, SychkaRust1 runs Rust network protocol 2306 and build 163794. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on SychkaRust1?
8 players, on average, was the busiest crowd at its recent wipes. 5 hours after the latest wipe, the crowd peaked.
On what timetable does SychkaRust1 run its wipes?
The rhythm of SychkaRust1 cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 34 days 11 hours is how long the current world has been running.
Server tags
What do the server tags on SychkaRust1 mean?
These are the tags SychkaRust1 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp200 (Max players): 200 slots are available; v2306 (Protocol): Your game needs to be on protocol 2306 to join; cs163794 (Build): The game build is 163794; ptrak (Networking): Network layer: RakNet, the standard for Rust; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; h14d047d1 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; stok (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does SychkaRust1 appear?
These Rust Server Trends lists include SychkaRust1: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z.
Connecting
How do you connect to SychkaRust1?
Enter client.connect 178.173.248.141:27002 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://anti-rust.gamestores.ru/#/app/store/.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.