Station XX-7865 · recording
Sandkasten
Online 147.93.162.142:29215 checked 9m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #7,865
- top 35%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 20h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +1into Tue 17:00 UTC
- Peak · 48 h
- 1most players in any hour
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 35% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 20hThu 5 Nov, 19:00 UTCFW
- 35d 20hThu 3 Dec, 19:00 UTCFW
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 |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:11 UTC FW27d ago | M0.0■steady | 0 | – | running | 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 Sandkasten?
The procedural map on Sandkasten is size 3,700 with seed 2064416874, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Sandkasten?
You will find no gather rate in the name of Sandkasten. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. It describes itself as vanilla, which means no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Sandkasten right now?
A reading taken now shows 0 players on Sandkasten, which has 50 slots. The seven-day average is 0 players, with a peak of 1. Averaged over the last 48 hours, the busiest hour was 17:00 UTC at 1 players.
How does Sandkasten rank against other Rust servers?
The last seven days of player hours place Sandkasten at #7,865, in the top 35% of all ranked servers.
Server facts
How reliably does Sandkasten stay online?
Sandkasten is up at the moment. The uptime it reports puts its last restart about 6 days 2 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does Sandkasten perform under load?
Its average server fps over the last 48 hours was 59, and it never dropped below 21. At its highest, it carried 74,340 entities: buildings, deployables and the world's other contents. Memory use peaked at 2,874 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does Sandkasten run from?
No region is published by Sandkasten. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 147.93.162.142:29215 is the address it uses.
Which Rust version is Sandkasten running?
Sandkasten is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Sandkasten?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.
How often does Sandkasten wipe, and on which days?
Once a month Sandkasten wipes, at the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 27 days 4 hours.
Server tags
What do the server tags on Sandkasten mean?
Tags published by Sandkasten and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it. 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 Sandkasten appear?
The Rust Server Trends lists that take in Sandkasten are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v; Group limit: 5 or more.
Join the server
What steps get you onto Sandkasten?
To join, enter client.connect 147.93.162.142:29215 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. For the website, go to https://www.youtube.com/watch?v=dQw4w9WgXcQ.
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.