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
You'll find no region listed by KOLA_LOX. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 89.209.57.168:28015.
How dependable is KOLA_LOX, and is it online at the moment?
The server is down: KOLA_LOX is offline now, with the last sighting 38 days 22 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 19 September 2026.
On what Rust version does KOLA_LOX sit?
You will find KOLA_LOX on Rust network protocol 2633 and build 163558, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does KOLA_LOX reset?
The record holds too few of KOLA_LOX's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 47 days 2 hours have passed since this world was made.
Population
Where does KOLA_LOX sit among Rust servers?
Over the last seven days, KOLA_LOX has #13,247 for player hours, in the top – of all ranked servers.
What does the population on KOLA_LOX look like?
The last sighting of KOLA_LOX was 38 days 22 hours ago, and it is offline right now.
Tags
What is meant by the tags on KOLA_LOX?
The game's browser takes its cue from the tags KOLA_LOX has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163558 (Build): Build number: 163558; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under 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 Rust Server Score filters and lists feature KOLA_LOX?
Rust Server Score lists that include KOLA_LOX: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on KOLA_LOX?
Nothing in the name of KOLA_LOX states a gather rate. The group limit stays at the game's default of 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. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
KOLA_LOX runs which map?
A procedural map, generated by the game, is what KOLA_LOX runs.
Connecting
What is the way to join KOLA_LOX?
To connect, start Rust, press F1, and type client.connect 89.209.57.168:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs163558,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163558
BuildBuild number: 163558.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.
Not enough figures yet to write a report. Check back after a few days on the list.