Station XX-16363 · no signal
TEST SERVER
Offline 194.147.90.159:35000 checked 33d ago
- Players now
- 0/ 600
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,363
- top 71%
- Last wipe
- 37d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 600 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, measured since 17 Sep. 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
- 3.7 daysbetween real wipes
- wipe-day peak
- 2players, 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 |
|---|---|---|---|---|---|---|
| Thu 17 Sep, 16:53 UTC41d ago | M0.0■steady | 0 | – | running | 0 | |
| Sun 13 Sep, 23:10 UTC45d ago | M0.3▲rising | 4 | halved by day 1 | 3.7 days | 2 |
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 TEST SERVER?
Generated by the game, the map on TEST SERVER is procedural, size 6,000 with seed 1337. Size and seed produce the same map, so RustMaps can show it from this page. Its map carries the name TEST MAP.
Which settings and rules apply on TEST SERVER?
You will find no gather rate in the name of TEST SERVER. 100000 players is the most a group can hold. In minigames & battle royale mode, battle royale, arenas, parkour and Bedwars. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on TEST SERVER right now?
TEST SERVER is not responding at this moment and is offline, last seen 33 days 21 hours ago.
How does TEST SERVER rank against other Rust servers?
On player hours for the past week, TEST SERVER sits at #16,363, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does TEST SERVER stay online?
As recorded now, TEST SERVER is not reachable, the last contact having been 33 days 21 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does TEST SERVER run from?
Nothing about a region comes from TEST SERVER. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 194.147.90.159:35000.
Which Rust version is TEST SERVER running?
On Windows, TEST SERVER runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on TEST SERVER?
On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 0 hours after the wipe. 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 TEST SERVER wipe, and on which days?
On record so far are too few of TEST SERVER's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 37 days 10 hours.
Server tags
What do the server tags on TEST SERVER mean?
Tags published by TEST SERVER and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp600 (Max players): 600 slots are available; ts100000 (Group limit): The team limit is 100000; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $rRU (Region code): The region code for this server is RU; ^e (Minigames): Minigames including arenas, Bedwars and parkour; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does TEST SERVER appear?
You will find TEST SERVER on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Minigames ^e, Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
How do you connect to TEST SERVER?
To join, enter client.connect 194.147.90.159:35000 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.