Jeremy Solo PvE
Offline 74.141.66.230:28015 checked 18d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes
Quick answers
Tags and search
Where does Jeremy Solo PvE appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Jeremy Solo PvE: Rust community servers, going deep and Go deep on PvE servers. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
What's the meaning of the tags on Jeremy Solo PvE?
gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): The slot count is 1; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs163493 (Build): It's on build 163493; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^p (PvE): No PvP here: the danger comes from the environment — that is the tag list Jeremy Solo PvE puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What's the location of Jeremy Solo PvE?
Jeremy Solo PvE does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 74.141.66.230:28015.
How reliable is Jeremy Solo PvE?
The server Jeremy Solo PvE is not reachable at the moment; the last sighting was 18 days 8 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 17 September 2026 is when Rust Going Deep first saw it.
What Rust version is Jeremy Solo PvE on?
On Windows, Jeremy Solo PvE runs Rust network protocol 2633 and build 163493. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Jeremy Solo PvE wipe?
The wipes recorded for Jeremy Solo PvE are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 38 days 5 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Jeremy Solo PvE running?
Its name does not state a gather rate for Jeremy Solo PvE. Up to 8 players per group, which is the default. It runs pve, no fighting other players. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on Jeremy Solo PvE?
The map on Jeremy Solo PvE is procedural, made by the game.
Player count
What's the population like on Jeremy Solo PvE?
Right now Jeremy Solo PvE is offline, with its last appearance 18 days 8 hours ago.
What position does Jeremy Solo PvE hold in the server rankings?
Over the last seven days, Jeremy Solo PvE is #15,455 by player hours, among the top 65% of all ranked servers.
Getting in
How do you get into Jeremy Solo PvE?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 74.141.66.230:28015.