Working its way up from the back of the class: #13,100 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
46/ 100
D
Slipped a little: down 944 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 61% 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 AxentHost.com Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 142.132.250.170:54369.
How dependable is AxentHost.com Server, and is it online at the moment?
The server is down: AxentHost.com Server is offline now, with the last sighting 15 days 23 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 October 2026, Rust Server Score saw it for the first time.
What Rust version is AxentHost.com Server on?
The server AxentHost.com Server is on Rust network protocol 2634 and build 167781 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does AxentHost.com Server reset?
There are too few wipes on record for AxentHost.com Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 15 days 23 hours.
Player count
Where does AxentHost.com Server place in the wider field of Rust servers?
Over the last seven days, AxentHost.com Server has #13,100 for player hours, in the top 61% of all ranked servers.
Is AxentHost.com Server a busy server?
The last sighting of AxentHost.com Server was 15 days 23 hours ago, and it is offline right now.
Tags and filters
What do AxentHost.com Server's tags stand for?
You'll see AxentHost.com Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server 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 AxentHost.com Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include AxentHost.com Server: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is AxentHost.com Server set up, and what rules does it keep?
You will find no gather rate in the name of AxentHost.com Server. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on AxentHost.com Server?
The game generates a procedural map for AxentHost.com Server.
Connecting
How do you get onto AxentHost.com Server?
To connect, start Rust, press F1, and type client.connect 142.132.250.170:54369. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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. Even marks across the subjects, from F to D.