Working its way up from the back of the class: #12,870 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
45/ 100
D
Slipped a little: down 1,188 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 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
You'll find no region listed by Nikitikita_server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 193.178.226.194:28015.
How dependable is Nikitikita_server, and is it online at the moment?
The server is down: Nikitikita_server is offline now, with the last sighting 13 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 15 October 2026.
Which Rust version is Nikitikita_server running?
The server Nikitikita_server is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Nikitikita_server reset?
The record holds too few of Nikitikita_server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 19 days 2 hours have passed since this world was made.
Player count
Where does Nikitikita_server sit among Rust servers?
In the top 59% of all ranked servers, Nikitikita_server sits at #12,870 for player hours over the last seven days.
How many players does Nikitikita_server usually have?
Nikitikita_server is offline at the moment; the last time it was seen was 13 days 18 hours ago.
Tags and filters
What do Nikitikita_server's tags stand for?
You'll see Nikitikita_server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here 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 Nikitikita_server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Nikitikita_server among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does Nikitikita_server enforce, and what are its settings?
You will find no gather rate in the name of Nikitikita_server. 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 under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Nikitikita_server runs which map?
The game generates a procedural map for Nikitikita_server.
How to join
How should you connect to Nikitikita_server?
To connect, start Rust, press F1, and type client.connect 193.178.226.194:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set 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.
A term to build on. Even marks across the subjects, from F to D.