Working its way up from the back of the class: #15,459 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
5/ 100
F
Lost ground: down 13,836 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.
AveragePeakWipe
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% 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 KAMASABA LAST. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 210.131.218.116:28015.
How reliable is KAMASABA LAST, and is it up?
At this moment, KAMASABA LAST is offline; the last time it was seen was 34 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does KAMASABA LAST sit?
The server KAMASABA LAST is on Rust network protocol 2633 and build 163207 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does KAMASABA LAST reset?
The record holds too few of KAMASABA LAST's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 51 days 23 hours have passed since this world was made.
Player numbers
Where does KAMASABA LAST place in the wider field of Rust servers?
Over the last seven days, KAMASABA LAST has #15,459 for player hours, in the top 71% of all ranked servers.
What does the population on KAMASABA LAST look like?
The last sighting of KAMASABA LAST was 34 days ago, and it is offline right now.
Tags
What do KAMASABA LAST's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp80 (Max players): 80 slots are available; 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; cs163207 (Build): The game build is 163207; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags KAMASABA LAST publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does KAMASABA LAST appear in the Rust Server Score lists and filters?
Rust Server Score lists that include KAMASABA LAST: 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.
Server rules
How is KAMASABA LAST set up, and what rules does it keep?
Nothing in the name of KAMASABA LAST states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on KAMASABA LAST?
KAMASABA LAST runs a game-generated procedural map at size 4,500, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
How to join
What is the way to join KAMASABA LAST?
Enter client.connect 210.131.218.116: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 asmp80,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp80
Max players80 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildThe game build is 163207.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).