Working its way up from the back of the class: #15,966 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
53/ 100
D
Moving up: up 955 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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/EU) Karadeniz 3X Solo/Duo/Trio?
No region tag appears for (TR/EU) Karadeniz 3X Solo/Duo/Trio, but the name suggests Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 57.128.22.87:25623.
How reliable is (TR/EU) Karadeniz 3X Solo/Duo/Trio, and is it up?
The server is down: (TR/EU) Karadeniz 3X Solo/Duo/Trio is offline now, with the last sighting 23 days 23 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is (TR/EU) Karadeniz 3X Solo/Duo/Trio on?
The server (TR/EU) Karadeniz 3X Solo/Duo/Trio is on Rust network protocol 2633 and build 165217 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
When does (TR/EU) Karadeniz 3X Solo/Duo/Trio wipe, and how often?
(TR/EU) Karadeniz 3X Solo/Duo/Trio has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 53 days.
Player numbers
Where does (TR/EU) Karadeniz 3X Solo/Duo/Trio place in the wider field of Rust servers?
Over the last seven days, (TR/EU) Karadeniz 3X Solo/Duo/Trio has #15,966 for player hours, in the top 71% of all ranked servers.
How many players does (TR/EU) Karadeniz 3X Solo/Duo/Trio usually have?
(TR/EU) Karadeniz 3X Solo/Duo/Trio is offline at the moment; the last time it was seen was 23 days 23 hours ago.
Tags
What is meant by the tags on (TR/EU) Karadeniz 3X Solo/Duo/Trio?
The game's browser takes its cue from the tags (TR/EU) Karadeniz 3X Solo/Duo/Trio has set: gmrust (Game mode): Survival in the standard Rust style; mp250 (Max players): Its slot count is 250; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 lists and filters on Rust Server Score show (TR/EU) Karadeniz 3X Solo/Duo/Trio?
These Rust Server Score lists count (TR/EU) Karadeniz 3X Solo/Duo/Trio among them: 3x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Map and rules
How is (TR/EU) Karadeniz 3X Solo/Duo/Trio set up, and what rules does it keep?
Going by its name, (TR/EU) Karadeniz 3X Solo/Duo/Trio runs 3x gather. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: 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. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map (TR/EU) Karadeniz 3X Solo/Duo/Trio uses?
A procedural map, generated by the game, is what (TR/EU) Karadeniz 3X Solo/Duo/Trio runs.
Getting in
How do you get onto (TR/EU) Karadeniz 3X Solo/Duo/Trio?
To connect, start Rust, press F1, and type client.connect 57.128.22.87:25623. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp250,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp250
Max playersIts slot count is 250.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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); standing is the one to work on (F).