On the class lists: F (38), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 2
Rank#7,779top 35% · #431 in EA
Last wipe5d agoweekly schedule
Next wipe1d 19hFri 30 Oct, 09:06 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
65/ 100
C+
Working its way up from the back of the class: #7,779 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 1 places this week.
A term to build on.
Strongest in standing (C+); population 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 35% of all ranked servers, top 78% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
····W··
····W··
····W··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 09:06 UTC, in 1d 19h.
Its weekly schedule tag · low confidence
usual gap6.8 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 4
Coming wipes
1d 19hFri 30 Oct, 09:06 UTC
8d 5hThu 5 Nov, 19:00 UTCFW
8d 19hFri 6 Nov, 09:06 UTC
15d 19hFri 13 Nov, 09:06 UTC
22d 19hFri 20 Nov, 09:06 UTC
29d 19hFri 27 Nov, 09:06 UTC
36d 5hThu 3 Dec, 19:00 UTCFW
36d 19hFri 4 Dec, 09:06 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 42 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 09:06 UTC5d ago
2
–
running
0
Fri 16 Oct, 09:06 UTC12d ago
1
halved by day 6
7 days
0
Fri 9 Oct, 19:14 UTC18d ago
2
halved by day 2
6.6 days
0
Fri 9 Oct, 09:04 UTC19d ago
2
–
0.4 days
0
Fri 2 Oct, 14:53 UTC25d ago
1
halved by day 3
6.8 days
0
Wed 23 Sep, 15:35 UTC34d ago
1
halved by day 5
9 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
Which region is SakhaPlay | KIT | TP | X3-4 based in?
You'll see SakhaPlay | KIT | TP | X3-4 listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 91.185.236.67:28015.
How reliable is SakhaPlay | KIT | TP | X3-4, and is it up?
You cannot join now: SakhaPlay | KIT | TP | X3-4 is offline, last seen 3 days 3 hours ago. It was up 63% of the time over the last 7 full days, 106 of 168 hours. It was first seen by Rust Server Score on 23 September 2026.
What Rust version is SakhaPlay | KIT | TP | X3-4 on?
You will find SakhaPlay | KIT | TP | X3-4 on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
When does SakhaPlay | KIT | TP | X3-4 wipe, and how often?
Its tag sets the prediction, as the record holds too few of SakhaPlay | KIT | TP | X3-4's wipes to confirm its schedule. Friday 30 October at 09:06 UTC is the date set for its next wipe. 5 days 4 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on SakhaPlay | KIT | TP | X3-4?
Recent wipes have peaked at 2 players on average. Peak numbers came 42 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Population
Where does SakhaPlay | KIT | TP | X3-4 place in the wider field of Rust servers?
Over the last seven days, SakhaPlay | KIT | TP | X3-4 has #7,779 for player hours, in the top 35% of all ranked servers and #431 in Asia.
What does the population on SakhaPlay | KIT | TP | X3-4 look like?
The last sighting of SakhaPlay | KIT | TP | X3-4 was 3 days 3 hours ago, and it is offline right now. It peaked at 2 and averaged 0 players over the last seven days.
Tags
What do SakhaPlay | KIT | TP | X3-4's tags stand for?
You'll see SakhaPlay | KIT | TP | X3-4 tagged with gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^s (Softcore): You keep some inventory when you die, as Facepunch's easier mode allows; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): You will find it under East Asia in the browser in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show SakhaPlay | KIT | TP | X3-4?
Rust Server Score lists that include SakhaPlay | KIT | TP | X3-4: 3x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Game mode: Softcore; Server tag: Weekly ^w, Softcore ^s, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 3x.
Rules and settings
How is SakhaPlay | KIT | TP | X3-4 set up, and what rules does it keep?
Going by its name, SakhaPlay | KIT | TP | X3-4 runs 3x gather. The group limit stays at the game's default of 8 players. softcore is the mode here, Facepunch's gentler mode: part of your loot stays with you. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
SakhaPlay | KIT | TP | X3-4 runs which map?
The game generates the procedural map on SakhaPlay | KIT | TP | X3-4 at size 4,000 with seed 2147483647. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto SakhaPlay | KIT | TP | X3-4?
To connect, start Rust, press F1, and type client.connect 91.185.236.67:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://steamcommunity.com/groups/SakhaPlay.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^s,EA,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^s
SoftcoreYou keep some inventory when you die, as Facepunch's easier mode allows.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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+); population is the one to work on (F).