Offline 210.131.218.116:28015 checked 35d ago
KAMASABA LAST
Connect
srv = rust.server("210.131.218.116:29015")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 37/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 47/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 37/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Player counts
What position does KAMASABA LAST take in the server rankings?
Rank #15,459 on seven-day player hours for KAMASABA LAST, within the top 71% of all ranked servers.
How many players does KAMASABA LAST hold at once?
KAMASABA LAST returns no live count at this refresh, having last been seen 35 days 6 hours ago.
Server data
What is the Rust version on KAMASABA LAST?
Version Rust network protocol 2633 and build 163207 on Linux is reported by KAMASABA LAST. Steam updates your game for you, but the protocol must match to join.
Is KAMASABA LAST up, and what does its uptime show?
Offline now for KAMASABA LAST, last seen 35 days 6 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does KAMASABA LAST run from?
There is no region published for KAMASABA LAST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 210.131.218.116:28015.
Settings and map
Which settings and rules does KAMASABA LAST run?
You will not find a gather rate in the string KAMASABA LAST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has KAMASABA LAST loaded?
KAMASABA LAST runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe schedule
When does KAMASABA LAST wipe, and how often?
A rhythm cannot be read from the wipes of KAMASABA LAST on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 53 days 5 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain KAMASABA LAST?
These Rust Data lists include KAMASABA LAST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on KAMASABA LAST?
The game's server browser reads these tags from KAMASABA LAST: gmrust (Game mode): Rust survival in its standard form; mp80 (Max players): 80 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to KAMASABA LAST?
Enter client.connect 210.131.218.116:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.