On the class lists: F (27), with population over 48 hours and no performance mark.
Players now0/ 2200% full
7-day average0peak –
Rank#15,335top 69%
Last wipe12d agoweekly schedule
Next wipe1d 0hFri 30 Oct, 15:17 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 220 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,335 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
49/ 100
D
Slipped a little: down 210 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, and #518 of the trio servers (top 83%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WWW
····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, 15:17 UTC, in 1d 0h.
Its weekly schedule tag · low confidence
usual gap1.4 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 1
Coming wipes
1d 0hFri 30 Oct, 15:17 UTC
7d 4hThu 5 Nov, 19:00 UTCFW
8d 0hFri 6 Nov, 15:17 UTC
15d 0hFri 13 Nov, 15:17 UTC
22d 0hFri 20 Nov, 15:17 UTC
29d 0hFri 27 Nov, 15:17 UTC
35d 4hThu 3 Dec, 19:00 UTCFW
36d 0hFri 4 Dec, 15:17 UTC
The first 48 hours of its last wipes
Fri 16 OctSun 11 OctSat 10 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 15:17 UTC12d ago
0
–
running
0
Sun 11 Oct, 21:25 UTC17d ago
2
halved by day 1
4.7 days
1
Sat 10 Oct, 12:49 UTC19d ago
9
–
1.4 days
1
Fri 9 Oct, 16:49 UTC19d ago
9
–
0.8 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
Where in the world is [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA?
You'll find no region listed by [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 191.44.68.101:40053.
Is [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA up, and how steady is its uptime?
At this moment, [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA is offline; the last time it was seen was 5 days 23 hours ago. For the last 7 full days, it was up 40 of 168 hours, or 24% of the time. On 9 October 2026, Rust Server Score saw it for the first time.
Which Rust version is [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA running?
Rust network protocol 2634 and build 167781 on Linux is what [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA wipe its map?
Its tag sets the prediction, as the record holds too few of [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA's wipes to confirm its schedule. Friday 30 October at 15:17 UTC is the date set for its next wipe. The world it runs now was created 12 days 23 hours. Its tags state that it wipes weekly.
What should you expect from wipe day on [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA?
Recent wipes have peaked at 4 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Population
Where does [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA sit among Rust servers?
In the top 69% of all ranked servers, [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA sits at #15,335 for player hours over the last seven days. It comes #518 among servers in the trio group.
What does the population on [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA look like?
It has been 5 days 23 hours since [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA was last seen, and it is offline right now. For the last seven days, the average number of players was 0.
Tags
How should you read the tags on [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA?
The game's browser takes its cue from the tags [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA has set: gmvanilla (Game mode): This is vanilla survival; mp220 (Max players): Its slot count is 220; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
How is [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA set up, and what rules does it keep?
[TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA sets gather at 2x, as its name suggests. You can have up to 3 players in a group (trio). You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA?
The game generates the procedural map on [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA at size 3,500 with seed 764346. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [TR] İSTİKLAL 2X | SOLO/DUO/TRIO | KIT | WIPE CUMA?
Enter client.connect 191.44.68.101:40053 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/9yNsTtAeV8.
Server tags
what each one means
Published asmp220,ptrak,$r?,v2634,^z,^y,^w,gmvanilla,cs167781,ts3
Game
gmvanilla
Game modeThis is vanilla survival.
mp220
Max playersIts slot count is 220.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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 momentum (D); population is the one to work on (F).