Working its way up from the back of the class: #15,833 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
26/ 100
F
Lost ground: down 7,636 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 72% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 10hThu 5 Nov, 19:00 UTCFW
35d 10hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
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
Thu 1 Oct, 23:16 UTCFW27d ago
1
–
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
In what location does My Debian 13 Rust Server sit?
No region is published for My Debian 13 Rust Server. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 140.177.168.95:28015.
How dependable is My Debian 13 Rust Server, and is it online at the moment?
At this moment, My Debian 13 Rust Server is offline; the last time it was seen was 19 days 9 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 13 September 2026.
Which Rust version is My Debian 13 Rust Server running?
Rust network protocol 2634 and build 166494 on Linux is what My Debian 13 Rust Server runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does My Debian 13 Rust Server reset?
The force wipe each month is the only wipe My Debian 13 Rust Server takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 27 days 9 hours have passed since this world was made.
What happens on My Debian 13 Rust Server when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does My Debian 13 Rust Server place in the wider field of Rust servers?
Over the last seven days, My Debian 13 Rust Server has #15,833 for player hours, in the top 72% of all ranked servers.
Is My Debian 13 Rust Server a busy server?
It has been 19 days 9 hours since My Debian 13 Rust Server was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on My Debian 13 Rust Server?
You'll see My Debian 13 Rust Server tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show My Debian 13 Rust Server?
Rust Server Score lists that include My Debian 13 Rust 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.
Rules and settings
Which rules does My Debian 13 Rust Server enforce, and what are its settings?
You will find no gather rate in the name of My Debian 13 Rust Server. The group limit stays at the game's default of 8 players. survival is the mode 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. The server does not run VAC, Valve's anti-cheat.
My Debian 13 Rust Server runs which map?
A procedural map, generated by the game, is what My Debian 13 Rust Server runs.
Connecting
How should you connect to My Debian 13 Rust Server?
To connect, start Rust, press F1, and type client.connect 140.177.168.95:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Even marks across the subjects, from F to F.