Station XX-13632 · no signal
Timeweb Cloud
Offline 217.25.228.235:28015 checked 18d ago
- Players now
- 1/ 5
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,632
- top 62%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 5 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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 2 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 00:02 UTC27d ago | M0.0■steady | 1 | – | running | 1 | |
| Tue 29 Sep, 15:38 UTC29d ago | M0.0▲rising | 1 | – | 2.4 days | 0 | |
| Mon 28 Sep, 01:10 UTC31d ago | M0.0▲rising | 1 | – | 1.6 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 pageServer rules
Which map is running on Timeweb Cloud?
Timeweb Cloud uses a procedural map, which the game generates.
Which settings and rules apply on Timeweb Cloud?
You will find no gather rate in the name of Timeweb Cloud. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on Timeweb Cloud?
Timeweb Cloud is not responding at this moment and is offline, last seen 18 days 13 hours ago.
How does Timeweb Cloud rank against other Rust servers?
The last seven days of player hours place Timeweb Cloud at #13,632, in the top 62% of all ranked servers.
Operator and location
How reliably does Timeweb Cloud stay online?
No contact with Timeweb Cloud right now, and the last recorded contact was 18 days 13 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 28 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Timeweb Cloud hosted?
No region is published by Timeweb Cloud. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 217.25.228.235:28015 is the address it uses.
What build of Rust does Timeweb Cloud use?
On Windows, Timeweb Cloud runs Rust network protocol 2634 and build 166494. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Timeweb Cloud?
On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does Timeweb Cloud wipe, and on which days?
There is no next wipe to predict at Timeweb Cloud, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 27 days 8 hours.
Tags
What do the server tags on Timeweb Cloud mean?
The game's server browser reads the tags Timeweb Cloud publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): 5 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 Timeweb Cloud appear?
These Rust Server Trends lists include Timeweb Cloud: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Timeweb Cloud?
To join, enter client.connect 217.25.228.235:28015 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.
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.