Working its way up from the back of the class: #16,275 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
49/ 100
D
Slipped a little: down 164 places this week. Nothing a good wipe can't fix.
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
AxentHost.com Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 142.132.250.170:59075 is the address to use.
Is AxentHost.com Server up, and how steady is its uptime?
At this moment, AxentHost.com Server is offline; the last time it was seen was 28 days 4 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 1 October 2026, Rust Server Score saw it for the first time.
On what Rust version does AxentHost.com Server sit?
The server AxentHost.com Server is on Rust network protocol 2633 and build 165217 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does AxentHost.com Server wipe its map?
AxentHost.com Server has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 28 days 5 hours have passed since this world was made.
Population
What position does AxentHost.com Server hold in the rankings?
In the top 69% of all ranked servers, AxentHost.com Server sits at #16,275 for player hours over the last seven days.
What does the population on AxentHost.com Server look like?
It has been 28 days 4 hours since AxentHost.com Server was last seen, and it is offline right now.
Lists and filters
What do AxentHost.com Server's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): 40 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags AxentHost.com Server publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show AxentHost.com Server?
Rust Server Score lists that include AxentHost.com Server: 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
How is AxentHost.com Server set up, and what rules does it keep?
The name of AxentHost.com Server gives no 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. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
AxentHost.com Server runs which map?
A procedural map, generated by the game, is what AxentHost.com Server runs.
How to join
How should you connect to AxentHost.com Server?
To connect, start Rust, press F1, and type client.connect 142.132.250.170:59075. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max players40 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).