Station XX-14258 · no signal
Pt|LusoTuga |Vanilla|Biweekly
Offline 203.16.163.235:28015 checked 34d ago
- Players now
- 2/ 100
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,258
- top 63%
- Last wipe
- 34d ago
- biweekly schedule
- Next wipe
- 7d 9h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 100 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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence
- wipe-day peak
- 2players, last three wipes
Coming wipes
- 7d 9hThu 5 Nov, 19:00 UTCFW
- 21d 8hThu 19 Nov, 18:42 UTC
- 35d 9hThu 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 2, 6 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 24 Sep, 18:42 UTC34d ago | M0.8▼falling | 2 | – | running | 9 |
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 Pt|LusoTuga |Vanilla|Biweekly?
Generated by the game, the map on Pt|LusoTuga |Vanilla|Biweekly is procedural, size 3,000 with seed 50000. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Pt|LusoTuga |Vanilla|Biweekly?
No gather rate appears in the name of Pt|LusoTuga |Vanilla|Biweekly. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on Pt|LusoTuga |Vanilla|Biweekly?
A reading taken now finds Pt|LusoTuga |Vanilla|Biweekly offline; the most recent activity was 34 days 8 hours ago.
How does Pt|LusoTuga |Vanilla|Biweekly rank against other Rust servers?
On player hours for the past week, Pt|LusoTuga |Vanilla|Biweekly sits at #14,258, which puts it inside the top 63% of every ranked server.
Operator and location
How reliably does Pt|LusoTuga |Vanilla|Biweekly stay online?
No contact with Pt|LusoTuga |Vanilla|Biweekly right now, and the last recorded contact was 34 days 8 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Pt|LusoTuga |Vanilla|Biweekly hosted?
No region is published by Pt|LusoTuga |Vanilla|Biweekly. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 203.16.163.235:28015 is the address it uses.
What build of Rust does Pt|LusoTuga |Vanilla|Biweekly use?
On Linux, Pt|LusoTuga |Vanilla|Biweekly runs Rust network protocol 2633 and build 165217. 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 Pt|LusoTuga |Vanilla|Biweekly?
2 players, on average, was the busiest crowd at its recent wipes. 6 hours after the latest wipe, the crowd peaked.
How often does Pt|LusoTuga |Vanilla|Biweekly wipe, and on which days?
The prediction is taken from its tag, since Pt|LusoTuga |Vanilla|Biweekly has too few wipes on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 34 days 10 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Tags
What do the server tags on Pt|LusoTuga |Vanilla|Biweekly mean?
Tags published by Pt|LusoTuga |Vanilla|Biweekly and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^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 Pt|LusoTuga |Vanilla|Biweekly appear?
The Rust Server Trends lists that take in Pt|LusoTuga |Vanilla|Biweekly are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Connecting
What steps get you onto Pt|LusoTuga |Vanilla|Biweekly?
To join, enter client.connect 203.16.163.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.