Working its way up from the back of the class: #15,941 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
25/ 100
F
Lost ground: down 8,054 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers, top 88% in EU. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The 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
EU · groups of 300+ · 2x · monthly · 146 on average
123 / 500
Quick answers
from the figures on this page
About the server
Which region is [TEST] RustBackEnd x2 | wipe 24.09 based in?
In Europe, according to its own listing, sits [TEST] RustBackEnd x2 | wipe 24.09, with the EU tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 144.31.67.179:28015 is the address to use.
How reliable is [TEST] RustBackEnd x2 | wipe 24.09, and is it up?
You cannot join now: [TEST] RustBackEnd x2 | wipe 24.09 is offline, last seen 23 days 18 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 24 September 2026.
On what Rust version does [TEST] RustBackEnd x2 | wipe 24.09 sit?
You will find [TEST] RustBackEnd x2 | wipe 24.09 on Rust network protocol 2633 and build 165217, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does [TEST] RustBackEnd x2 | wipe 24.09 wipe, and how often?
the force wipe gives the basis for estimating [TEST] RustBackEnd x2 | wipe 24.09's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 34 days 18 hours. The tags show a monthly wipe schedule.
Population
What position does [TEST] RustBackEnd x2 | wipe 24.09 hold in the rankings?
In Europe, [TEST] RustBackEnd x2 | wipe 24.09 is #2,518, and overall it is #15,941 on player hours over the last seven days, in the top 71% of all ranked servers.
What does the population on [TEST] RustBackEnd x2 | wipe 24.09 look like?
It has been 23 days 18 hours since [TEST] RustBackEnd x2 | wipe 24.09 was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [TEST] RustBackEnd x2 | wipe 24.09?
You'll see [TEST] RustBackEnd x2 | wipe 24.09 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): In the server browser it appears under Europe 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.
Which lists and filters on Rust Server Score show [TEST] RustBackEnd x2 | wipe 24.09?
Rust Server Score lists that include [TEST] RustBackEnd x2 | wipe 24.09: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Rules and settings
What settings and rules apply on [TEST] RustBackEnd x2 | wipe 24.09?
[TEST] RustBackEnd x2 | wipe 24.09 sets gather at 2x, as its name suggests. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: 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.
Can you tell me which map [TEST] RustBackEnd x2 | wipe 24.09 uses?
A procedural map of size 3,000 and seed 2018866553, generated by the game, is what [TEST] RustBackEnd x2 | wipe 24.09 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto [TEST] RustBackEnd x2 | wipe 24.09?
Enter client.connect 144.31.67.179: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 asmp100,ptrak,$r?,v2633,^z,^y,^m,EU,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeIn the server browser it appears under Europe.
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.