Working its way up from the back of the class: #15,108 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
52/ 100
D
Moving up: up 681 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.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 17 Sep, 16:52 UTC40d ago
0
–
running
0
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
Where in the world is Rust 400 | Rail-Ready Standard Map?
Rust 400 | Rail-Ready Standard Map leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 176.43.253.48:28015.
Is Rust 400 | Rail-Ready Standard Map up, and how steady is its uptime?
At this moment, Rust 400 | Rail-Ready Standard Map is offline; the last time it was seen was 12 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Rust 400 | Rail-Ready Standard Map sit?
Rust network protocol 2632 and build 161125 on Windows is what Rust 400 | Rail-Ready Standard Map runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Rust 400 | Rail-Ready Standard Map reset?
There are too few wipes on record for Rust 400 | Rail-Ready Standard Map to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 68 days 21 hours have passed since this world was made.
What should you expect from wipe day on Rust 400 | Rail-Ready Standard Map?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player count
Where does Rust 400 | Rail-Ready Standard Map sit among Rust servers?
In the top 70% of all ranked servers, Rust 400 | Rail-Ready Standard Map sits at #15,108 for player hours over the last seven days.
Is Rust 400 | Rail-Ready Standard Map a busy server?
The last sighting of Rust 400 | Rail-Ready Standard Map was 12 days 3 hours ago, and it is offline right now.
Tags and filters
What do Rust 400 | Rail-Ready Standard Map's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp400 (Max players): The server holds 400 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs161125 (Build): The game build is 161125; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server are the tags Rust 400 | Rail-Ready Standard Map 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 Rust 400 | Rail-Ready Standard Map?
Rust Server Score lists that include Rust 400 | Rail-Ready Standard Map: 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
What settings and rules apply on Rust 400 | Rail-Ready Standard Map?
You will find no gather rate in the name of Rust 400 | Rail-Ready Standard Map. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Rust 400 | Rail-Ready Standard Map runs which map?
The game generates a procedural map for Rust 400 | Rail-Ready Standard Map.
Getting in
What is the way to join Rust 400 | Rail-Ready Standard Map?
Enter client.connect 176.43.253.48: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 asmp400,ptrak,$r?,v2632,gmrust,cs161125,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp400
Max playersThe server holds 400 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs161125
BuildThe game build is 161125.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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. Strongest in momentum (D); standing is the one to work on (F).