Rust StatisticsWorking papers on every public Rust server · 33,864 players now

Poly Sandbox (test)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 24d ago · 86.29.218.233:28025

Abstract

We describe the public Rust server Poly Sandbox (test), reached at 86.29.218.233:28025. It is offline at the last check, against a seven-day mean of 01. It ranks #15,975 of all servers, the top 71%. It last wiped 25d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,975top 71%
Last wipe25d 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 71% 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
15k10k15k20k20 Sep24 Sep28 Sep3 Oct7 Oct11 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 gap10.2 daysbetween real wipes
Wipe-day peak0players, last three wipes
Crowd held0%else halves by day 1
Sat 3 OctWed 23 Sep
01234+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 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 3 Oct, 21:1325d ago 0 – running 0
Wed 23 Sep, 16:4635d ago 1 halved by day 1 10.2 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

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address86.29.218.233:28025
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe3 Oct 2026, 21:13 UTC
Hostname–
First seen13 Sep 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 modded server list with rates [2], creative and sandbox servers [3] and predicted wipe schedule [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |EU · groups of 8+ · 116 on average45/999
[NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |NA · groups of 8+ · 90 on average149/999
[AU] Rusticated.com - Creative Sandbox | Build | Never WipesOC · groups of 8+ · 52 on average62/150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFAEU · groups of 30+ · weekly · 37 on average7/100
AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 24 on average5/100
KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfightgroups of 8+ · 23 on average25/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Poly Sandbox (test)?

No region is published by Poly Sandbox (test). The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 86.29.218.233:28025 is its address.

A.2How reliable is Poly Sandbox (test), and is it currently online?

Poly Sandbox (test) is currently offline, with the last sighting 24 days 3 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.

A.3What is the Rust version for Poly Sandbox (test)?

Rust network protocol 2634 and build 166652 is the version that Poly Sandbox (test) runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4What schedule does Poly Sandbox (test) follow for wipes?

Too few wipes by Poly Sandbox (test) have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The world currently in use was created 25 days 6 hours ago.

A.5How would you describe wipe day on Poly Sandbox (test)?

Across its recent wipes, the average peak population was 0 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 0% of recent wipes. In the other cases, the population fell below half by day 1.

Player count

A.6How does Poly Sandbox (test) compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Poly Sandbox (test) at #15,975, within the top 71% of ranked servers.

A.7What is the population level of Poly Sandbox (test)?

Poly Sandbox (test) is not online now; 24 days 3 hours have passed since it was last seen.

Tags and filters

A.8How should the tags on Poly Sandbox (test) be interpreted?

gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): It offers 10 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166652 (Build): Build 166652 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Poly Sandbox (test) publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can Poly Sandbox (test) be found among the Rust Statistics lists and filters?

Modded Rust servers and Build and creative servers in Rust are the Rust Statistics lists that Poly Sandbox (test) fits. It appears under the following filters on the server list: 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 Poly Sandbox (test)?

No gather rate appears in the name of Poly Sandbox (test). The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.11What map is in use on Poly Sandbox (test)?

A procedural map, generated by the game, is what Poly Sandbox (test) runs.

Connection

A.12What steps are required to join Poly Sandbox (test)?

Press F1 inside Rust to open the console and enter client.connect 86.29.218.233:28025. 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 mp10,ptrak,$r?,v2634,gmvanilla,cs166652,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. The mode is vanilla survival.
mp10Max players. It offers 10 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166652Build. Build 166652 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Creative and sandbox servers. ruststatistics.org/top-rust-build-servers.
  4. [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.