Working its way up from the back of the class: #8,973 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
32/ 100
F
Lost ground: down 3,252 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (C); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.3 daysbetween real wipes
wipe-day peak8players, last three wipes
The first 48 hours of its last wipes
Thu 24 SepThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 8, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 24 Sep, 22:00 UTC34d ago
8
–
running
0
Thu 24 Sep, 14:27 UTC34d ago
8
–
0.3 days
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for SychkaRust1. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 178.173.248.141:27002.
How dependable is SychkaRust1, and is it online at the moment?
You cannot join now: SychkaRust1 is offline, last seen 34 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 24 September 2026.
What Rust version is SychkaRust1 on?
Rust network protocol 2306 and build 163794 on Linux is what SychkaRust1 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does SychkaRust1 reset?
The record holds too few of SychkaRust1's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 34 days 7 hours have passed since this world was made.
What should you expect from wipe day on SychkaRust1?
Across its recent wipes, the busiest moments averaged 8 players. Peak numbers came 5 hours into the latest wipe.
Player count
Where does SychkaRust1 sit among Rust servers?
In the top 40% of all ranked servers, SychkaRust1 sits at #8,973 for player hours over the last seven days.
What does the population on SychkaRust1 look like?
It has been 34 days 2 hours since SychkaRust1 was last seen, and it is offline right now.
Lists and filters
What do SychkaRust1's tags stand for?
The game's browser takes its cue from the tags SychkaRust1 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp200 (Max players): 200 slots are available; v2306 (Protocol): The game protocol is 2306, so your game must match that version to join; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet handles it, the game's default network layer; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; h14d047d1 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner; stok (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature SychkaRust1?
Rust Server Score lists that include SychkaRust1: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z.
Server rules
How is SychkaRust1 set up, and what rules does it keep?
The name of SychkaRust1 gives no gather rate. It publishes no limit on group size. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. You are covered by VAC, Valve's anti-cheat.
Which map is in play on SychkaRust1?
The game generates the procedural map on SychkaRust1 at size 3,000 with seed 233782. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to SychkaRust1?
Enter client.connect 178.173.248.141:27002 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://anti-rust.gamestores.ru/#/app/store/.
Server tags
what each one means
Published asmp200,ptrak,v2306,h14d047d1,stok,gmrust,cs163794,^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp200
Max players200 slots are available.
v2306
ProtocolThe game protocol is 2306, so your game must match that version to join.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h14d047d1
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
stok
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in standing (C); momentum is the one to work on (F).