Working its way up from the back of the class: #13,504 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 295 places this week.
A term to build on.
Strongest in momentum (D); wipes are 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.
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
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WWW··
··W····
W······
····W·W
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Sun 11 OctFri 9 OctMon 28 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 20:16 UTC18d ago
1
–
running
0
Fri 9 Oct, 16:00 UTC20d ago
0
–
2.2 days
1
Mon 28 Sep, 16:58 UTC31d ago
1
–
11 days
0
Mon 28 Sep, 03:04 UTC31d ago
1
–
0.6 days
1
Wed 23 Sep, 21:16 UTC35d ago
1
–
4.2 days
0
Fri 18 Sep, 15:15 UTC41d ago
1
halved by day 1
5.3 days
1
Fri 18 Sep, 04:08 UTC41d ago
1
–
0.5 days
1
Thu 17 Sep, 01:43 UTC42d ago
1
–
1.1 days
1
Wed 16 Sep, 19:07 UTC43d ago
1
–
0.3 days
1
Wed 16 Sep, 03:04 UTC43d ago
1
–
0.7 days
1
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
NA · groups of 12+ · 1000x · biweekly · 2 on average
0 / 100
Quick answers
from the figures on this page
About the server
In what location does Azure - Battlefield | 1000x | Face Checks | Free For All sit?
You'll find no region listed by Azure - Battlefield | 1000x | Face Checks | Free For All. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 207.255.38.119:28015.
Is Azure - Battlefield | 1000x | Face Checks | Free For All up, and how steady is its uptime?
At this moment, Azure - Battlefield | 1000x | Face Checks | Free For All is offline; the last time it was seen was 18 days ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 15 September 2026, Rust Server Score saw it for the first time.
What Rust version is Azure - Battlefield | 1000x | Face Checks | Free For All on?
Rust network protocol 2634 and build 166586 on Windows is what Azure - Battlefield | 1000x | Face Checks | Free For All runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Azure - Battlefield | 1000x | Face Checks | Free For All reset?
Azure - Battlefield | 1000x | Face Checks | Free For All wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 18 days have passed since this world was made.
What happens on Azure - Battlefield | 1000x | Face Checks | Free For All when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player numbers
What position does Azure - Battlefield | 1000x | Face Checks | Free For All hold in the rankings?
In the top 61% of all ranked servers, Azure - Battlefield | 1000x | Face Checks | Free For All sits at #13,504 for player hours over the last seven days.
What does the population on Azure - Battlefield | 1000x | Face Checks | Free For All look like?
Azure - Battlefield | 1000x | Face Checks | Free For All is offline at the moment; the last time it was seen was 18 days ago.
Tags and filters
How should you read the tags on Azure - Battlefield | 1000x | Face Checks | Free For All?
The game's browser takes its cue from the tags Azure - Battlefield | 1000x | Face Checks | Free For All has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp475 (Max players): 475 slots are available; ts0 (Group limit): The team system is turned off; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): Build number: 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 Azure - Battlefield | 1000x | Face Checks | Free For All appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Azure - Battlefield | 1000x | Face Checks | Free For All: Rust servers above 10x gather rate, Modded Rust servers, graded and Rust battlefield servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Gather rate: More than 10x.
Map and rules
Which rules does Azure - Battlefield | 1000x | Face Checks | Free For All enforce, and what are its settings?
The name of Azure - Battlefield | 1000x | Face Checks | Free For All points to a 1000x gather rate. You will find no published group limit. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Getting in
What is the way to join Azure - Battlefield | 1000x | Face Checks | Free For All?
To connect, start Rust, press F1, and type client.connect 207.255.38.119:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp475,ptrak,$r?,v2634,gmrust,cs166586,ts0,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp475
Max players475 slots are available.
ts0
Group limitThe team system is turned off.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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); wipes are the one to work on (F).