Working its way up from the back of the class: #15,383 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
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
22/ 100
F
Lost ground: down 8,637 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (F); momentum 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
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·····W·
W·W·W··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 19:16 UTC, in 1d 19h.
Its weekly schedule tag · low confidence
usual gap2 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak1players, last three wipes
crowd held33%else halves by day 5.5
Coming wipes
1d 19hFri 30 Oct, 19:16 UTC
7d 19hThu 5 Nov, 19:00 UTCFW
8d 19hFri 6 Nov, 19:16 UTC
15d 19hFri 13 Nov, 19:16 UTC
22d 19hFri 20 Nov, 19:16 UTC
29d 19hFri 27 Nov, 19:16 UTC
35d 19hThu 3 Dec, 19:00 UTCFW
36d 19hFri 4 Dec, 19:16 UTC
The first 48 hours of its last wipes
Fri 16 OctWed 14 OctWed 14 Oct
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
Fri 16 Oct, 19:16 UTC12d ago
1
–
running
0
Wed 14 Oct, 17:27 UTC14d ago
1
✓ held half
2.1 days
0
Wed 14 Oct, 08:40 UTC14d ago
1
–
0.4 days
0
Mon 12 Oct, 13:59 UTC16d ago
1
–
1.8 days
0
Sat 10 Oct, 13:49 UTC18d ago
1
halved by day 1
2 days
0
Mon 21 Sep, 14:31 UTC37d ago
1
halved by day 10
19 days
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 RustNN | X10 | Kit | Zombe | RB sit?
RustNN | X10 | Kit | Zombe | RB 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 78.40.188.44:28015.
How dependable is RustNN | X10 | Kit | Zombe | RB, and is it online at the moment?
You cannot join now: RustNN | X10 | Kit | Zombe | RB is offline, last seen 8 days 4 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 21 September 2026, Rust Server Score saw it for the first time.
What Rust version is RustNN | X10 | Kit | Zombe | RB on?
Rust network protocol 2634 and build 167781 on Windows is what RustNN | X10 | Kit | Zombe | RB runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does RustNN | X10 | Kit | Zombe | RB wipe, and how often?
Its tag sets the prediction, as the record holds too few of RustNN | X10 | Kit | Zombe | RB's wipes to confirm its schedule. It is due to wipe next on Friday 30 October at 19:16 UTC. The world it runs now was created 12 days 4 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on RustNN | X10 | Kit | Zombe | RB?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 33% of its recent wipes. Day 5.5 is when it sank below half in the wipes that did not hold.
Population
What position does RustNN | X10 | Kit | Zombe | RB hold in the rankings?
Over the last seven days, RustNN | X10 | Kit | Zombe | RB has #15,383 for player hours, in the top 70% of all ranked servers.
Is RustNN | X10 | Kit | Zombe | RB a busy server?
RustNN | X10 | Kit | Zombe | RB is offline at the moment; the last time it was seen was 8 days 4 hours ago.
Tags and filters
What do RustNN | X10 | Kit | Zombe | RB's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptsw (Networking): This server uses 'sw' as its network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags RustNN | X10 | Kit | Zombe | RB publishes, and the game's server browser reads them. 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 RustNN | X10 | Kit | Zombe | RB?
Rust Server Score lists that include RustNN | X10 | Kit | Zombe | RB: 10x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 10x.
Map and rules
How is RustNN | X10 | Kit | Zombe | RB set up, and what rules does it keep?
RustNN | X10 | Kit | Zombe | RB sets gather at 10x, as its name suggests. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
RustNN | X10 | Kit | Zombe | RB runs which map?
The game generates a procedural map for RustNN | X10 | Kit | Zombe | RB.
Connecting
How should you connect to RustNN | X10 | Kit | Zombe | RB?
To connect, start Rust, press F1, and type client.connect 78.40.188.44:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptsw,$r?,v2634,^w,^v,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max players40 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptsw
NetworkingThis server uses 'sw' as its network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 wipe hold (F); momentum is the one to work on (F).