Offline 37.113.209.189:28015 checked 43d ago
LocalSolo3500
Connect
srv = rust.server("37.113.209.189:28016")
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. 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 bestWipe 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 1, 23 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 14 Sep, 20:02 UTC44d ago | 1 | NaN | running | 0 |
| 1 | Sun 13 Sep, 20:55 UTC45d ago | 1 | NaN | 1 days | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 37.113.209.189:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Sep 2026, 20:02 UTC
- hostname
- –
- first seen
- 13 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 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 53/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population
What position does LocalSolo3500 take in the server rankings?
Rank #13,327 on seven-day player hours for LocalSolo3500, within the top – of all ranked servers.
What population does LocalSolo3500 carry?
LocalSolo3500 returns no live count at this refresh, having last been seen 43 days 8 hours ago.
Server facts
Which Rust version is LocalSolo3500 on?
The build is Rust network protocol 2633 and build 163794 on Windows, run by LocalSolo3500. The protocol has to match before you can join, and Steam does the updating.
How reliable is LocalSolo3500, and is it up?
LocalSolo3500 is offline at this refresh; the last response came 43 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does LocalSolo3500 sit?
No region is published by LocalSolo3500. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.113.209.189:28015 is its address.
Rules, settings, map
Which rules apply on LocalSolo3500, and what settings?
No gather rate appears in the name: LocalSolo3500. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on LocalSolo3500?
LocalSolo3500 runs a procedural map, which the game generates.
Wipes and dates
On what schedule does LocalSolo3500 wipe?
A rhythm cannot be read from the wipes of LocalSolo3500 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 44 days 8 hours ago, and that is the one in play.
What is wipe day on LocalSolo3500 like?
Across recent wipes the busiest point averaged 1 players. 23 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain LocalSolo3500?
On Rust Data, LocalSolo3500 appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on LocalSolo3500?
The game's server browser reads these tags from LocalSolo3500: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into LocalSolo3500?
Enter client.connect 37.113.209.189:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.