Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
No daily history yet.
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
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
In what location does [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio sit?
The name of [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio points to Europe, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 212.129.84.114:28015 is the address to use.
Is [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio up, and how steady is its uptime?
You cannot join now: [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio is offline, last seen 38 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio sit?
You will find [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio on Rust network protocol 2633 and build 164530, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio wipe its map?
There are too few wipes on record for [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 52 days 16 hours have passed since this world was made.
Player numbers
What position does [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio hold in the rankings?
In the top – of all ranked servers, [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio sits at #15,468 for player hours over the last seven days.
Is [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio a busy server?
It has been 38 days 5 hours since [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio was last seen, and it is offline right now.
Tags and filters
What do [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio's tags stand for?
You'll see [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the server. 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 [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio: 3x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 3x.
Server rules
Which rules does [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio enforce, and what are its settings?
Going by its name, [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio runs 3x gather. With no change from the game default, groups take up to 8 players. 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 Carbon. VAC, Valve's anti-cheat, is enabled.
[EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio runs which map?
[EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio runs a procedural map, which the game generates.
How to join
What is the way to join [EU] KurdLabs 3x | 3 DAY WIPE | Solo/Duo/Trio?
Enter client.connect 212.129.84.114:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs164530,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.
Not enough figures yet to write a report. Check back after a few days on the list.