Online 85.236.190.20:28015 checked 10m ago
locServ47
Connect
srv = rust.server("85.236.190.20:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 06:11 UTC26d ago | 3 | NaN | 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.
display(srv.map, srv.info())
Map
3000 · seed 3221155
- map
- Procedural Map
- size
- 3000
- seed
- 3221155
Server
srv.info()- address
- 85.236.190.20:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 06:17 UTC
- hostname
- –
- first seen
- 23 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 434/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 457/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 281 on average | 981/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 64/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 989/1000 |
| 5 | Rustoria.co - US Main | NA · groups of 16+ · weekly · 236 on average | 23/250 |
Quick answers
From the figures on this page.
Population data
How does locServ47 compare in the rankings?
Over the last seven days locServ47 sits at #5,866 on player hours, in the top 26% of ranked servers.
How many players does locServ47 hold at once?
The sample now reads 0 players for locServ47, out of 20 slots. Over the last seven days it averaged 0 players and peaked at 3. The 48-hour sample puts the busiest hour at 05:00 UTC, averaging 1 players.
About the server
How smoothly does locServ47 run?
Averaged over 48 hours: 187 server fps, never under 147. Entity numbers reached 48,444, and that includes buildings, deployables and the rest. Memory peaked at 2,391 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does locServ47 run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by locServ47. Joining needs the same protocol on your game; Steam handles the update.
Is locServ47 up, and what does its uptime show?
Online is the state at the latest refresh for locServ47. Count back 5 days 8 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 23 September 2026.
Which location does locServ47 run from?
There is no region published for locServ47. Rust Data does not look up where the machine stands; it shows where a server says it is. 85.236.190.20:28015 is its address.
Rules, settings, map
Which settings and rules does locServ47 run?
No gather rate appears in the name: locServ47. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has locServ47 loaded?
Size 3,000, seed 3221155: the procedural map on locServ47, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does locServ47 wipe, and how often?
The record for locServ47 holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 26 days 9 hours ago.
On locServ47, what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. 29 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold locServ47, and which filters?
The Rust Data lists that locServ47 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on locServ47 hold?
The game's server browser reads these tags from locServ47: gmvanilla (Game mode): Survival in vanilla form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to locServ47?
In Rust, F1 opens the console: type client.connect 85.236.190.20:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.
