Working its way up from the back of the class: #13,592 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
30/ 100
F
Lost ground: down 5,511 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 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW·W
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sun 18 OctFri 16 OctThu 15 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
Sun 18 Oct, 08:09 UTC11d ago
1
–
running
1
Fri 16 Oct, 19:06 UTC12d ago
1
–
1.5 days
0
Thu 15 Oct, 18:57 UTC13d ago
1
–
1 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
No region is published for Joehoe6767. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 5.135.198.197:25593 is the address to use.
How dependable is Joehoe6767, and is it online at the moment?
You cannot join now: Joehoe6767 is offline, last seen 11 days 6 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 15 October 2026.
On what Rust version does Joehoe6767 sit?
You will find Joehoe6767 on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Joehoe6767 wipe its map?
Joehoe6767 wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 11 days 6 hours.
What should you expect from wipe day on Joehoe6767?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Joehoe6767 place in the wider field of Rust servers?
In the top 62% of all ranked servers, Joehoe6767 sits at #13,592 for player hours over the last seven days.
Is Joehoe6767 a busy server?
It has been 11 days 6 hours since Joehoe6767 was last seen, and it is offline right now.
Lists and filters
What do Joehoe6767's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts6 (Group limit): Teams cap out at 6; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Joehoe6767 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 Joehoe6767?
These Rust Server Score lists count Joehoe6767 among them: 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; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does Joehoe6767 enforce, and what are its settings?
Nothing in the name of Joehoe6767 states a gather rate. A group here can reach 6 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Joehoe6767 uses?
Joehoe6767 runs a game-generated procedural map at size 4,000, seed 55369. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to Joehoe6767?
Enter client.connect 5.135.198.197:25593 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 asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts6,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts6
Group limitTeams cap out at 6.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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. Even marks across the subjects, from F to F.