Working its way up from the back of the class: #14,543 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
40/ 100
F
Slipped a little: down 2,833 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 61% 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
EU · groups of 300+ · 2x · weekly · 297 on average
96 / 1000
Quick answers
from the figures on this page
Server details
Where in the world is Kavkaz Rust X2 Trio | Hapis TEST?
No region is published for Kavkaz Rust X2 Trio | Hapis TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 83.219.97.64:28015 is the address to use.
Is Kavkaz Rust X2 Trio | Hapis TEST up, and how steady is its uptime?
You cannot join now: Kavkaz Rust X2 Trio | Hapis TEST is offline, last seen 29 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 28 September 2026, Rust Server Score saw it for the first time.
What Rust version is Kavkaz Rust X2 Trio | Hapis TEST on?
Rust network protocol 2633 and build 165217 on Windows is what Kavkaz Rust X2 Trio | Hapis TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Kavkaz Rust X2 Trio | Hapis TEST wipe its map?
There are too few wipes on record for Kavkaz Rust X2 Trio | Hapis TEST 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. 29 days 14 hours have passed since this world was made.
Player numbers
Where does Kavkaz Rust X2 Trio | Hapis TEST place in the wider field of Rust servers?
Over the last seven days, Kavkaz Rust X2 Trio | Hapis TEST has #14,543 for player hours, in the top 61% of all ranked servers.
How many players does Kavkaz Rust X2 Trio | Hapis TEST usually have?
Kavkaz Rust X2 Trio | Hapis TEST is offline at the moment; the last time it was seen was 29 days 12 hours ago.
Tags and filters
What is meant by the tags on Kavkaz Rust X2 Trio | Hapis TEST?
You'll see Kavkaz Rust X2 Trio | Hapis TEST tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; jp0 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. 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 Kavkaz Rust X2 Trio | Hapis TEST appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Kavkaz Rust X2 Trio | Hapis TEST among them: 2x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.
Rules and settings
What settings and rules apply on Kavkaz Rust X2 Trio | Hapis TEST?
Kavkaz Rust X2 Trio | Hapis TEST sets gather at 2x, as its name suggests. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Getting in
What is the way to join Kavkaz Rust X2 Trio | Hapis TEST?
To connect, start Rust, press F1, and type client.connect 83.219.97.64:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,jp0,$r?,v2633,gmrust,cs165217,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
Other
jp0
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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. Even marks across the subjects, from F to F.