scott
Offline 15.204.65.147:29315 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 24/200
- 32/200
- 20/200
- 9/150
- 32/200
- 10/100
Quick answers
from the figures on this pageWipe schedule
What wipe timing does scott follow?
To tell the rhythm of scott, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 53 days 14 hours ago the current world was made.
Lists and filters
Which tags does scott carry, and what do they mean?
Tags published by scott, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): Game build reading: 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^p (PvE): No fighting between players: the world itself is the hazard. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show scott?
These Rust Metrics lists carry scott: Rust community servers: live readings and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Occupancy
Where does scott sit in the rankings?
Ranking for scott: #15,025 on seven-day player hours, top – of all ranked servers.
What is the population on scott?
Reading for scott: offline at this moment; last seen 44 days 22 hours ago.
Server
Which location does scott run from?
No region tag on scott. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 15.204.65.147:29315.
What Rust version is scott on?
Reading: scott, Rust network protocol 2633 and build 163207, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is scott up, and how often does it stay up?
scott reports offline. The last reading came 44 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does scott enforce, and what are its settings?
Reading the name gives no gather rate for scott. 8 players per group, the default value. pve, no combat against other players — that is the game mode. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on scott?
Procedural map on scott, made by the game's generator.
Connection
How do you connect to scott?
Press F1 in Rust and enter client.connect 15.204.65.147:29315. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.