On the class lists: F (28), with population over 48 hours and no performance mark.
Players now0/ 600% full
7-day average0peak 1
Rank#10,435top 47%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 60 on average. Plenty of space to grow.
Standingrank on player hours
53/ 100
D
Working its way up from the back of the class: #10,435 on player hours.
Uptimehours on the list, last 48
25/ 100
F
Attendance needs work: on the list only 12 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 69 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 3,196 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); population 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 47% 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
No region is published for VonBehr. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 98.142.14.57:28015.
How reliable is VonBehr, and is it up?
You cannot join now: VonBehr is offline, last seen 36 hours ago. The uptime it reports puts the last restart at about 9 days 17 hours ago. For the last 7 full days, it was up 152 of 168 hours, or 90% of the time. It was first seen by Rust Server Score on 3 October 2026.
How well does VonBehr run?
It averaged 69 server fps over the last 48 hours, with a low of 58. Buildings, deployables and everything else in the world added up to as many as 88,197 entities. At its highest, it used 4,239 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is VonBehr on?
The server VonBehr is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does VonBehr wipe, and how often?
VonBehr has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 25 days 6 hours.
Player numbers
Where does VonBehr place in the wider field of Rust servers?
Over the last seven days, VonBehr has #10,435 for player hours, in the top 47% of all ranked servers.
What does the population on VonBehr look like?
VonBehr is offline at the moment; the last time it was seen was 36 hours ago. The seven-day average is 0 players, with a peak of 1.
Tags
What do VonBehr's tags stand for?
The game's browser takes its cue from the tags VonBehr has set: gmvanilla (Game mode): This is vanilla survival; mp60 (Max players): Its slot count is 60; 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): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Where does VonBehr appear in the Rust Server Score lists and filters?
Rust Server Score lists that include VonBehr: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on VonBehr?
You will find no gather rate in the name of VonBehr. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: 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. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
VonBehr runs which map?
VonBehr runs a game-generated procedural map at size 4,000, seed 711856267. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to VonBehr?
To connect, start Rust, press F1, and type client.connect 98.142.14.57:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp60,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp60
Max playersIts slot count is 60.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is 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 performance (A+); population is the one to work on (F).