Working its way up from the back of the class: #13,101 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
27/ 100
F
Lost ground: down 6,058 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
AveragePeak
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 59% 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
No region is published for özelbölüm. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 195.174.160.132:28015 is the address to use.
Is özelbölüm up, and how steady is its uptime?
The server is down: özelbölüm is offline now, with the last sighting 8 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 October 2026, Rust Server Score saw it for the first time.
Which Rust version is özelbölüm running?
Rust network protocol 2634 and build 166586 on Windows is what özelbölüm runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does özelbölüm wipe its map?
The record holds too few of özelbölüm's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 15 days 6 hours.
Population
Where does özelbölüm place in the wider field of Rust servers?
Over the last seven days, özelbölüm has #13,101 for player hours, in the top 59% of all ranked servers.
What does the population on özelbölüm look like?
özelbölüm is offline at the moment; the last time it was seen was 8 days 4 hours ago.
Tags
What do özelbölüm's tags stand for?
You'll see özelbölüm tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): Its slot count is 1; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166586 (Build): The game build is 166586; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server 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 özelbölüm appear in the Rust Server Score lists and filters?
These Rust Server Score lists count özelbölüm among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on özelbölüm?
The name of özelbölüm gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map özelbölüm uses?
A procedural map, generated by the game, is what özelbölüm runs.
How to join
How should you connect to özelbölüm?
Enter client.connect 195.174.160.132: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 asmp1,ptrak,$r?,v2634,gmrust,cs166586,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersIts slot count is 1.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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 standing (F); momentum is the one to work on (F).