locServ47
Online 85.236.190.20:28015 checked 9m ago
Server instruments
last reading Wed 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 143 · below 20 is lag, below 10 is badEntities
48 h range 45,805–48,485 · memory 1,999 MBUptime
4 days 15 hours since its last restart, at the last readingPlayers
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, measured since 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 27% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 29 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 06:11 UTC25d ago | 3 | – | running | 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
the same kind of game, then region, group limit, rate and wipes- 395/500
- 242/300
- 41/250
- 31/250
- 69/100
- 80/200
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on locServ47?
The busiest point of its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 29 hours.
When does locServ47 wipe?
Its rhythm cannot be told from the wipes of locServ47 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 25 days 16 hours ago.
Tags
How should you read the tags on locServ47?
Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp20 (Max players): Slots: 20; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from locServ47. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show locServ47?
On Rust Metrics, locServ47 sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does locServ47 sit in the rankings?
Ranking for locServ47: #5,979 on seven-day player hours, top 27% of all ranked servers.
What is the population on locServ47?
0 of 20 slots are filled on locServ47 right now. Seven-day check: 0 players on average. Peak reading: 3. The last 48 hours peaked at 07:00 UTC, averaging 1 players at that hour.
Server
Which location does locServ47 run from?
Reading: location. locServ47 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 85.236.190.20:28015.
What Rust version is locServ47 on?
Rust network protocol 2635 and build 168909 on Linux is the build locServ47 runs. Matching protocol is required to join. Let Steam update your game.
Is performance on locServ47 within range?
Check: fps. Average 186 server fps over the last 48 hours, low of 143. Within range. Peak entity count: 48,485. Buildings, deployables and all else included. Memory peak: 2,206 MB. What players call lag comes from low fps and an entity count on the rise.
Is locServ47 up, and how often does it stay up?
locServ47 reports online. Status: normal. Reading: uptime. About 4 days 15 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 23 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on locServ47?
No gather rate appears in the name: locServ47. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on locServ47?
Size 3,000 and seed 3221155: the game generates the procedural map on locServ47 from them. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How do you connect to locServ47?
Press F1 in Rust and enter client.connect 85.236.190.20:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.