StatusLive Servers online11,720 Players57,954 Populated3,334 Wiped · 3 h174 Interval5 min Date29 OCT 2026

DWG RG-S14258Server sheetchecked 34d ago

Pt|LusoTuga |Vanilla|Biweekly

Offline 203.16.163.235:28015 checked 34d ago

biweekly wipes vanillamoddedcarbon
Connect
Players now 2/ 100 2% full
7-day average0peak –
Rank#14,258top 63%
Last wipe34d agobiweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on Pt|LusoTuga |Vanilla|Biweekly
Fig. 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 Oct

Top 63% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe · high confidence

wipe-day peak2players, last three wipes

Coming wipes

  1. 7d 8hThu 5 Nov, 19:00 UTCFW
  2. 21d 7hThu 19 Nov, 18:42 UTC
  3. 35d 8hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 2, 6 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 42 on average
14 / 100
02
[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 16 on average
10 / 100
03
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average
8 / 200
04
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average
9 / 200
05 5 / 50
06 2 / 50
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

Is Pt|LusoTuga |Vanilla|Biweekly online, and what uptime has been recorded?

Pt|LusoTuga |Vanilla|Biweekly is offline at this moment; 34 days 9 hours ago is when it was last seen. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

In which location is Pt|LusoTuga |Vanilla|Biweekly hosted?

There is no region published by Pt|LusoTuga |Vanilla|Biweekly. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 203.16.163.235:28015 is its address.

On which Rust version is Pt|LusoTuga |Vanilla|Biweekly running?

Rust network protocol 2633 and build 165217 on Linux: that is what Pt|LusoTuga |Vanilla|Biweekly runs. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on Pt|LusoTuga |Vanilla|Biweekly?

The latest refresh records Pt|LusoTuga |Vanilla|Biweekly as offline, last seen 34 days 9 hours ago.

Against other Rust servers, where is Pt|LusoTuga |Vanilla|Biweekly placed?

Within the top 63% of all ranked servers: Pt|LusoTuga |Vanilla|Biweekly at #14,258 for player hours, seven days recorded.

Wipe data

On Pt|LusoTuga |Vanilla|Biweekly, what does the data show for wipe day?

An average of 2 players was recorded at the busiest point of its recent wipes. 6 hours after the latest wipe, the crowd peaked.

On Pt|LusoTuga |Vanilla|Biweekly, when do wipes occur?

The prediction follows its tag, because too few wipes of Pt|LusoTuga |Vanilla|Biweekly are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 34 days 11 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Map and rules

What settings and rules apply on Pt|LusoTuga |Vanilla|Biweekly?

No gather rate is stated in the name of Pt|LusoTuga |Vanilla|Biweekly. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Carbon. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat: VAC, from Valve, is on.

What is the map for Pt|LusoTuga |Vanilla|Biweekly?

Seed 50000 and size 3,000 define the procedural map Pt|LusoTuga |Vanilla|Biweekly generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Lists and filters

On Rust Graphs, which lists and filters contain Pt|LusoTuga |Vanilla|Biweekly?

On Rust Graphs, Pt|LusoTuga |Vanilla|Biweekly is placed in these lists: Modded Rust servers. On the server list, these filters bring it up: 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.

On Pt|LusoTuga |Vanilla|Biweekly, what is meant by each tag?

The game's server browser reads these tags from Pt|LusoTuga |Vanilla|Biweekly: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): The slot count is 100; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): To join, your game must be on protocol 2633; cs165217 (Build): Build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

What is the way to connect to Pt|LusoTuga |Vanilla|Biweekly?

Connect with client.connect 203.16.163.235:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^z,^y,^b,^v,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players The slot count is 100.
ts8
Group limit The default team size of 8 applies.
v2633
Protocol To join, your game must be on protocol 2633.
cs165217
Build Build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon The plugin framework is Carbon.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

KeyTag string decoded