Working its way up from the back of the class: #15,989 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
48/ 100
D
Slipped a little: down 760 places this week. Nothing a good wipe can't fix.
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 71% of all ranked servers. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
You'll find no region listed by RUST@FRITTENBUDE. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 87.122.62.159:28015.
Is RUST@FRITTENBUDE up, and how steady is its uptime?
The server is down: RUST@FRITTENBUDE is offline now, with the last sighting 24 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does RUST@FRITTENBUDE sit?
You will find RUST@FRITTENBUDE on Rust network protocol 2634 and build 166652, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does RUST@FRITTENBUDE reset?
The record holds too few of RUST@FRITTENBUDE's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 25 days 12 hours.
Population
Where does RUST@FRITTENBUDE sit among Rust servers?
Over the last seven days, RUST@FRITTENBUDE has #15,989 for player hours, in the top 71% of all ranked servers.
What does the population on RUST@FRITTENBUDE look like?
The last sighting of RUST@FRITTENBUDE was 24 days 21 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on RUST@FRITTENBUDE?
The game's browser takes its cue from the tags RUST@FRITTENBUDE has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships 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@FRITTENBUDE?
These Rust Server Score lists count RUST@FRITTENBUDE among them: Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v; Group limit: 5 or more.
Map and rules
What settings and rules apply on RUST@FRITTENBUDE?
The name of RUST@FRITTENBUDE gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RUST@FRITTENBUDE uses?
The game generates a procedural map for RUST@FRITTENBUDE.
Connecting
What is the way to join RUST@FRITTENBUDE?
Enter client.connect 87.122.62.159: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 asmp50,ptrak,$r?,v2634,^v,gmrust,cs166652,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
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).