Working its way up from the back of the class: #13,196 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
36/ 100
F
Slipped a little: down 3,770 places this week. Nothing a good wipe can't fix.
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 61% of all ranked servers, top 83% 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 5h.
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
In Europe, according to its own listing, sits FZB_TEST, with the EU tag. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 80.11.228.226:28015.
How dependable is FZB_TEST, and is it online at the moment?
At this moment, FZB_TEST is offline; the last time it was seen was 16 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 6 October 2026.
What Rust version is FZB_TEST on?
Rust network protocol 2634 and build 167584 on Windows is what FZB_TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does FZB_TEST reset?
The next wipe on FZB_TEST is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 23 days 6 hours. Its tags record that it wipes monthly.
Player count
Where does FZB_TEST sit among Rust servers?
Over the last seven days, FZB_TEST has #13,196 for player hours, in the top 61% of all ranked servers and #2,423 in Europe.
Is FZB_TEST a busy server?
FZB_TEST is offline at the moment; the last time it was seen was 16 days 1 hours ago.
Lists and filters
What do FZB_TEST's tags stand for?
The game's browser takes its cue from the tags FZB_TEST has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): Its slot count is 5; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167584 (Build): The game build is 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EU (Europe): In the server browser it appears under Europe. 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 FZB_TEST?
These Rust Server Score lists count FZB_TEST among them: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
How is FZB_TEST set up, and what rules does it keep?
Nothing in the name of FZB_TEST states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map FZB_TEST uses?
The game generates a procedural map for FZB_TEST.
Connecting
How do you get onto FZB_TEST?
To connect, start Rust, press F1, and type client.connect 80.11.228.226: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,^m,EU,gmrust,cs167584,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersIts slot count is 5.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167584
BuildThe game build is 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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.