LocalSolo3500
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 43d ago · 37.113.209.189:28015
Abstract
We describe the public Rust server LocalSolo3500, reached at 37.113.209.189:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,327 of all servers. It last wiped 44d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Usual gap | 1 days | between real wipes |
| Wipe-day peak | 1 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Mon 14 Sep, 20:0244d ago | 1 | – | running | 0 |
| Sun 13 Sep, 20:5545d ago | 1 | – | 1 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| 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 |
| Map | Procedural Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and upcoming Rust wipes [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 150 on average | 80/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 126/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average | 121/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average | 41/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average | 4/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average | 14/1000 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1What is the location of LocalSolo3500?
There is no region published for LocalSolo3500. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 37.113.209.189:28015.
A.2How reliable is LocalSolo3500, and is it currently online?
Right now, LocalSolo3500 is offline, and the last time it was seen was 43 days 11 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 13 September 2026.
A.3What version of Rust is run on LocalSolo3500?
Rust network protocol 2633 and build 163794 is the version that LocalSolo3500 runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.4When are wipes carried out on LocalSolo3500?
The record of LocalSolo3500's wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 44 days 11 hours have passed since the current world was generated.
A.5What happens on LocalSolo3500 when wipe day arrives?
The average busiest point of recent wipes was 1 players. The crowd reached its maximum 23 hours after the latest wipe.
Player count
A.6What is the rank of LocalSolo3500 among Rust servers?
Ranked by player hours across seven days, LocalSolo3500 holds #13,327, in the top – of all ranked servers.
A.7At what level does LocalSolo3500 operate in terms of players?
LocalSolo3500 is not online now; 43 days 11 hours have passed since it was last seen.
Tags and filters
A.8What do the tags associated with LocalSolo3500 signify?
Tags from LocalSolo3500, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp5 (Max players): The slot count is 5; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs163794 (Build): Build 163794 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.9Where can LocalSolo3500 be found among the Rust Statistics lists and filters?
Modded Rust servers are the Rust Statistics lists that LocalSolo3500 fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules, settings, map
A.10What are the settings and rules that govern LocalSolo3500?
Its name carries no gather rate for LocalSolo3500. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.
A.11On which map does LocalSolo3500 take place?
The game generates the map on LocalSolo3500; that format is procedural.
How to join
A.12How do you connect to LocalSolo3500?
Press F1 inside Rust to open the console and enter client.connect 37.113.209.189:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp5,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp5 | Max players. The slot count is 5. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2633 | Protocol. The game protocol is 2633; your client must match it to join. |
cs163794 | Build. Build 163794 is the one running. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. No region code is set. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.