Rust StatisticsWorking papers on every public Rust server · 43,056 players now

My Solo Sandbox

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 2d ago · 109.145.45.110:28015

Abstract

We describe the public Rust server My Solo Sandbox, reached at 109.145.45.110:28015. It is offline at the last check, against a seven-day mean of 1 and a peak of 11. It ranks #5,614 of all servers, the top 25%. It last wiped 2d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/1100% full
In the queue0no queue
Seven-day mean1peak 1
Rank2#5,614top 25%
Last wipe2d agono schedule published
Next wipe3–too few wipes seen yet

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.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

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).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 25% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
12k4k6k8k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap2.3 daysbetween real wipes
Wipe-day peak1players, last three wipes
Crowd held100%of its cycles kept half the crowd
Mon 26 OctSat 24 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 18:382d ago 1 – running 1
Sat 24 Oct, 10:584d ago 1 held half 2.3 d 1

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

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address109.145.45.110:28015
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe26 Oct 2026, 19:12 UTC
Hostname–
First seen24 Oct 2026
MapProcedural 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 build servers listed live [2], community tab servers measured [3] and predicted wipe schedule [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
【南瓜】Build-TestEA · groups of 8+ · 10 on average7/101
Raichu Staging | F1 Spawn | Noclip | DLC UnlockedEU · groups of 8+ · 2 on average0/25
[EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |EU · groups of 8+ · 115 on average128/999
[NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |NA · groups of 8+ · 90 on average201/999
[AU] Rusticated.com - Creative Sandbox | Build | Never WipesOC · groups of 8+ · 52 on average56/150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFAEU · groups of 30+ · weekly · 37 on average22/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does My Solo Sandbox have?

There is no region published for My Solo Sandbox. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 109.145.45.110:28015.

A.2How reliable is My Solo Sandbox, and is it currently online?

At the present moment, My Solo Sandbox is offline; it was last seen 2 days 5 hours ago. Its uptime over the last full days (4 days) was 16%, with 15 of 96 hours online. It was first observed on 24 October 2026 by Rust Statistics.

A.3What version of Rust is run on My Solo Sandbox?

My Solo Sandbox is running Rust network protocol 2635 and build 168909 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does My Solo Sandbox follow for wipes?

Too few wipes by My Solo Sandbox have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 2 days 6 hours.

A.5What characterises wipe day on My Solo Sandbox?

Across its recent wipes, the average peak population was 1 players. The peak on the latest wipe came 0 hours after it began. The crowd stayed above half its peak until the next wipe in 100% of recent wipes.

Population

A.6What is the rank of My Solo Sandbox among Rust servers?

The seven-day player-hours ranking puts My Solo Sandbox at #5,614, within the top 25% of ranked servers.

A.7How would you characterise the player activity on My Solo Sandbox?

At this moment My Solo Sandbox is offline, having last been seen 2 days 5 hours ago. Averaged over the last seven days: 1 players; the same period peaks at 1.

Tags, lists

A.8How should the tags on My Solo Sandbox be interpreted?

gmrust (Game mode): This is survival as standard Rust plays; mp1 (Max players): The slot count is 1; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset: these are the tags My Solo Sandbox publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can My Solo Sandbox be found among the Rust Statistics lists and filters?

Build and creative servers in Rust and Rust community servers, measured are the Rust Statistics lists that My Solo Sandbox fits. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Rules, settings, map

A.10Under what rules and settings does My Solo Sandbox operate?

Its name carries no gather rate for My Solo Sandbox. At 8 players, the group limit equals the game's default. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. It is a community server, as the browser's Community listing shows. VAC, Valve's anti-cheat, is enabled.

A.11What map is in use on My Solo Sandbox?

A procedural map, generated by the game, is what My Solo Sandbox runs.

Connection

A.12What steps are required to join My Solo Sandbox?

Press F1 inside Rust to open the console and enter client.connect 109.145.45.110: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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp1Max players. The slot count is 1.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. The game build is 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.

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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Build servers listed live. ruststatistics.org/top-rust-build-servers.
  3. [3]Rust Statistics. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
  4. [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.