On the class lists: F (41), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 4
Rank#5,418top 24% · #1778 in EU
Last wipe17h agobiweekly schedule
Next wipe8d 5hThu 5 Nov, 19:00 UTC FW
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
76/ 100
B
Holds a respectable place: #5,418 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 249 server fps on average.
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
31/ 100
F
Lost ground: down 2,006 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (A+); 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
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 24% of all ranked servers, top 61% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
···F···
·······
·W·····
·······
·W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Thursday 5 November, 19:00 UTC, in 8d 5h.
The force wipe · high confidence
usual gap12.1 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak8players, last three wipes
crowd held0%else halves by day 3
Coming wipes
8d 5hThu 5 Nov, 19:00 UTCFW
11d 9hSun 8 Nov, 23:26 UTC
23d 13hSat 21 Nov, 03:00 UTC
36d 5hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Tue 13 OctThu 1 OctSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 5, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 19:52 UTC17h ago
–
–
running
0
Tue 13 Oct, 21:41 UTC14d ago
5
halved by day 2
13.9 days
0
Thu 1 Oct, 18:07 UTCFW26d ago
7
halved by day 6
12.1 days
0
Sun 20 Sep, 17:33 UTC37d ago
11
halved by day 3
11 days
2
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
EU · groups of 300+ · 2x · biweekly · 36 on average
15 / 100
Quick answers
from the figures on this page
About the server
In what location does KIPISH |X2|WIPE(27.10) sit?
The EU tag on KIPISH |X2|WIPE(27.10) puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. 5.42.211.31:35367 is the address to use.
Is KIPISH |X2|WIPE(27.10) up, and how steady is its uptime?
You can join now: KIPISH |X2|WIPE(27.10) is online. The uptime it reports puts the last restart at about 3 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does KIPISH |X2|WIPE(27.10) run?
It never fell below 131 server fps in the last 48 hours, averaging 311. Up to 97,796 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,357 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is KIPISH |X2|WIPE(27.10) running?
Rust network protocol 2635 and build 168909 on Windows is what KIPISH |X2|WIPE(27.10) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does KIPISH |X2|WIPE(27.10) wipe, and how often?
About every 12.1 days, KIPISH |X2|WIPE(27.10) has wiped lately. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 17 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on KIPISH |X2|WIPE(27.10)?
The average peak on its recent wipes was 8 players. 20 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Player count
What position does KIPISH |X2|WIPE(27.10) hold in the rankings?
Over the last seven days, KIPISH |X2|WIPE(27.10) has #5,418 for player hours, in the top 24% of all ranked servers and #1,778 in Europe.
Is KIPISH |X2|WIPE(27.10) a busy server?
Right now, 0 players are on KIPISH |X2|WIPE(27.10), which has 100 slots. It peaked at 4 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 10:00 UTC, averaging 4 players.
Lists and filters
What do KIPISH |X2|WIPE(27.10)'s tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): In the server browser it appears under Europe are the tags KIPISH |X2|WIPE(27.10) publishes, and the game's server browser reads them. 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.
Where does KIPISH |X2|WIPE(27.10) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count KIPISH |X2|WIPE(27.10) among them: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours; Gather rate: 2x.
Rules and settings
Which rules does KIPISH |X2|WIPE(27.10) enforce, and what are its settings?
KIPISH |X2|WIPE(27.10) sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
KIPISH |X2|WIPE(27.10) runs which map?
A procedural map of size 4,500 and seed 1337, generated by the game, is what KIPISH |X2|WIPE(27.10) runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Connecting
How should you connect to KIPISH |X2|WIPE(27.10)?
To connect, start Rust, press F1, and type client.connect 5.42.211.31:35367. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://t.me/+s7a26cRawSAyZWZi.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^z,^y,^b,EU,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeIn the server browser it appears under Europe.
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 performance (A+); population is the one to work on (F).