Working its way up from the back of the class: #15,281 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
51/ 100
D
Moving up: up 160 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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 69% 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 ABABA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 176.214.206.237:28015.
How reliable is ABABA, and is it up?
At this moment, ABABA is offline; the last time it was seen was 9 days 19 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 19 October 2026.
On what Rust version does ABABA sit?
Rust network protocol 2631 and build 158240 on Windows is what ABABA runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does ABABA wipe its map?
The record holds too few of ABABA's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 87 days 12 hours.
Player count
What position does ABABA hold in the rankings?
Over the last seven days, ABABA has #15,281 for player hours, in the top 69% of all ranked servers.
What does the population on ABABA look like?
The last sighting of ABABA was 9 days 19 hours ago, and it is offline right now.
Tags
How should you read the tags on ABABA?
You'll see ABABA tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2631 (Protocol): The game protocol is 2631, so your game must match that version to join; cs158240 (Build): The game build is 158240; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here 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 ABABA appear in the Rust Server Score lists and filters?
Rust Server Score lists that include ABABA: 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.
Server rules
What settings and rules apply on ABABA?
The name of ABABA gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
ABABA runs which map?
A procedural map, generated by the game, is what ABABA runs.
How to join
What is the way to join ABABA?
Enter client.connect 176.214.206.237: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 asmp10,ptrak,$r?,v2631,gmrust,cs158240,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2631
ProtocolThe game protocol is 2631, so your game must match that version to join.
cs158240
BuildThe game build is 158240.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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. Strongest in momentum (D); standing is the one to work on (F).