Station XX-15975 · no signal
Poly Sandbox (test)
Offline 86.29.218.233:28025 checked 24d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,975
- top 71%
- Last wipe
- 25d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 10.2 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
- crowd held
- 0%else halves by day 1
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 21:13 UTC25d ago | M0.0■steady | 0 | – | running | 0 | |
| Wed 23 Sep, 16:46 UTC35d ago | M0.0▲rising | 1 | halved by day 1 | 10.2 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Poly Sandbox (test)?
A procedural map runs on Poly Sandbox (test), generated by the game.
Which settings and rules apply on Poly Sandbox (test)?
No gather rate appears in the name of Poly Sandbox (test). At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on Poly Sandbox (test)?
Poly Sandbox (test) is not responding at this moment and is offline, last seen 24 days 5 hours ago.
How does Poly Sandbox (test) rank against other Rust servers?
On player hours for the past week, Poly Sandbox (test) sits at #15,975, which puts it inside the top 71% of every ranked server.
Operator and location
How reliably does Poly Sandbox (test) stay online?
No contact with Poly Sandbox (test) right now, and the last recorded contact was 24 days 5 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does Poly Sandbox (test) run from?
No region is published by Poly Sandbox (test). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 86.29.218.233:28025.
What build of Rust does Poly Sandbox (test) use?
Poly Sandbox (test) is running Rust network protocol 2634 and build 166652 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Poly Sandbox (test)?
On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
How often does Poly Sandbox (test) wipe, and on which days?
On record so far are too few of Poly Sandbox (test)'s wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 25 days 7 hours.
Server tags
What do the server tags on Poly Sandbox (test) mean?
The game's server browser reads the tags Poly Sandbox (test) publishes: gmvanilla (Game mode): Survival in vanilla mode; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Poly Sandbox (test) appear?
You will find Poly Sandbox (test) on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust build and creative servers, live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Poly Sandbox (test)?
You can connect by pressing F1 in Rust and typing client.connect 86.29.218.233:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.