Station XX-15474 · no signal
Local test server (qos-priority)
Offline 77.21.168.254:29715 checked 11d ago
- Players now
- 0/ 200
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,474
- top 71%
- Last wipe
- 11d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 200 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.
- wipe-day peak
- 0players, last three wipes
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 |
|---|---|---|---|---|---|---|
| Tue 10 Nov, 06:15 UTC11d 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 pageServer rules
Which map is running on Local test server (qos-priority)?
A procedural map runs on Local test server (qos-priority), generated by the game.
Which settings and rules apply on Local test server (qos-priority)?
The name of Local test server (qos-priority) gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. The server has VAC off, Valve's anti-cheat.
Player counts
How many players are recorded on Local test server (qos-priority) right now?
Local test server (qos-priority) is not responding at this moment and is offline, last seen 11 days 6 hours ago.
How does Local test server (qos-priority) rank against other Rust servers?
On player hours for the past week, Local test server (qos-priority) sits at #15,474, which puts it inside the top 71% of every ranked server.
Operator and location
How reliably does Local test server (qos-priority) stay online?
Local test server (qos-priority) is down at the moment; the last recorded contact was 11 days 6 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 10 November 2026.
Which region does Local test server (qos-priority) run from?
A region is not published by Local test server (qos-priority). 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 77.21.168.254:29715.
What build of Rust does Local test server (qos-priority) use?
Local test server (qos-priority) is running Rust network protocol 2636 on a machine with macOS. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Local test server (qos-priority)?
0 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
How often does Local test server (qos-priority) wipe, and on which days?
The rhythm of Local test server (qos-priority) cannot yet be told: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 11 days 6 hours.
Server tags
What do the server tags on Local test server (qos-priority) mean?
Tags published by Local test server (qos-priority) and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp200 (Max players): The server has 200 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): Game protocol 2636: to join, your game must match this version; cs (Build): You won't find a published build number; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. 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 Local test server (qos-priority) appear?
These Rust Server Trends lists include Local test server (qos-priority): Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
What steps get you onto Local test server (qos-priority)?
You can connect by pressing F1 in Rust and typing client.connect 77.21.168.254:29715 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.