Pt|LusoTuga |Vanilla|Biweekly
Offline 203.16.163.235:28015 checked 34d ago
Server instruments
no direct query in 48 hoursPlayers now
2% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 3h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 3hFW
- WPT 2Thu 19 Nov, 18:42 UTC21d 3h
- WPT 3Thu 3 Dec, 19:00 UTC35d 3hFW
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 24 Sep, 18:42 UTC34d ago | 2 | – | running | 9 |
Peak: the most players in the first 48 hours. 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 wipes- 19/100
- 15/100
- 7/200
- 9/200
- 2/50
- 1/50
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Pt|LusoTuga |Vanilla|Biweekly?
At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 6 hours in.
How often does Pt|LusoTuga |Vanilla|Biweekly wipe, and when?
The prediction follows its tag, because too few of Pt|LusoTuga |Vanilla|Biweekly's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 34 days 16 hours ago. A wipe schedule of every two weeks is published in its tags.
Tag meanings
How should you read the tags on Pt|LusoTuga |Vanilla|Biweekly?
These are the tags Pt|LusoTuga |Vanilla|Biweekly publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Pt|LusoTuga |Vanilla|Biweekly?
Rust Metrics lists featuring Pt|LusoTuga |Vanilla|Biweekly: Modded Rust servers, checked live. These filters bring it up 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.
Occupancy
Where does Pt|LusoTuga |Vanilla|Biweekly sit in the rankings?
Ranking for Pt|LusoTuga |Vanilla|Biweekly: #14,258 on seven-day player hours, top 63% of all ranked servers.
What is the population on Pt|LusoTuga |Vanilla|Biweekly?
Pt|LusoTuga |Vanilla|Biweekly is not responding; status offline, last seen 34 days 14 hours ago.
Server details
What location is Pt|LusoTuga |Vanilla|Biweekly hosted in?
No region tag on Pt|LusoTuga |Vanilla|Biweekly. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 203.16.163.235:28015.
What Rust version is Pt|LusoTuga |Vanilla|Biweekly on?
Rust network protocol 2633 and build 165217 on Linux is the build Pt|LusoTuga |Vanilla|Biweekly runs. To get in, your game needs the same protocol; Steam applies the update.
Is Pt|LusoTuga |Vanilla|Biweekly up, and how often does it stay up?
Pt|LusoTuga |Vanilla|Biweekly reports offline. The last reading came 34 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
How is Pt|LusoTuga |Vanilla|Biweekly configured, and what rules are in force?
Check: gather rate. The name Pt|LusoTuga |Vanilla|Biweekly does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Vanilla is the label it uses: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. VAC is on. That is Valve's anti-cheat.
Which map is live on Pt|LusoTuga |Vanilla|Biweekly?
Size 3,000 and seed 50000: the game generates the procedural map on Pt|LusoTuga |Vanilla|Biweekly from them. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How do you connect to Pt|LusoTuga |Vanilla|Biweekly?
To join: start Rust, press F1 and type client.connect 203.16.163.235:28015. Or press Launch Rust here and Steam opens the game and connects you.