Working its way up from the back of the class: #15,455 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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 65% 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 Jeremy Solo PvE. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 74.141.66.230:28015 is the address to use.
Is Jeremy Solo PvE up, and how steady is its uptime?
You cannot join now: Jeremy Solo PvE is offline, last seen 28 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Jeremy Solo PvE running?
You will find Jeremy Solo PvE on Rust network protocol 2633 and build 163493, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Jeremy Solo PvE wipe its map?
There are too few wipes on record for Jeremy Solo PvE to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 48 days 8 hours.
Population
Where does Jeremy Solo PvE sit among Rust servers?
Over the last seven days, Jeremy Solo PvE has #15,455 for player hours, in the top 65% of all ranked servers.
How many players does Jeremy Solo PvE usually have?
Jeremy Solo PvE is offline at the moment; the last time it was seen was 28 days 11 hours ago.
Lists and filters
What do Jeremy Solo PvE's tags stand for?
The game's browser takes its cue from the tags Jeremy Solo PvE has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163493 (Build): The game build is 163493; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other. 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 Jeremy Solo PvE appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Jeremy Solo PvE: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Server rules
What settings and rules apply on Jeremy Solo PvE?
The name of Jeremy Solo PvE gives no gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Jeremy Solo PvE uses?
A procedural map, generated by the game, is what Jeremy Solo PvE runs.
How to join
How do you get onto Jeremy Solo PvE?
To connect, start Rust, press F1, and type client.connect 74.141.66.230:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,^p,gmrust,cs163493,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163493
BuildThe game build is 163493.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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.