[LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10
Offline SA 186.49.163.252:28015 checked 12h ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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 28 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 68% of all ranked servers, top 85% in SA. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Next wipe Friday 30 October, 21:13 UTC, in 1d 0h. Biweekly: 14 days after its last wipe
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What is the wipe schedule on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
An estimate from biweekly: 14 days after its last wipe gives [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10's next wipe. Friday 30 October at 21:13 UTC is when its next wipe is due. 12 days 23 hours ago the server made the world it is on now. The tags declare one wipe every two weeks.
Population
How busy is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
[LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 went quiet 12 hours ago and is offline right now. A seven-day average of 0 players.
How does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 rank against other Rust servers?
On player hours over the last seven days, [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 is #15,269 globally (top 68%) and #204 in South America.
Map and rules
Which map does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 run?
The map on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 is procedural, size 4,000 with seed 15565093, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page.
What are the rules and settings on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
No gather rate appears in the name [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10. Groups can contain up to 8 players, the default in the game. The server runs survival, standard play: gathering, building and raiding. Combat between players and raiding are both possible. You will find it under Community in the server browser; it is a community server. Vanilla is the server's own description: unchanged rates, kits and rules: the game in Facepunch's own form. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 run?
Rust network protocol 2634 and build 167781 on Linux is what [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 runs. Steam updates your game for you, and the protocol has to match for you to join.
Is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 online, and how reliable is it?
Offline at the moment: [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 was last seen 12 hours ago. Its reported uptime dates the last restart to about 12 days 9 hours ago. The first record of it on Rust Heatmap is 28 October 2026.
Where is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 located?
The SA tag is how [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 lists itself in South America. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 186.49.163.252:28015 is its address.
Does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 run smoothly?
Average server fps over the last 48 hours was 30; it never dropped below 30. Buildings, deployables and the rest of the world came to as much as 98,267 entities. At its peak it held 4,161 MB of memory. What players call lag is low fps together with a growing entity count.
Tags
Which Rust Heatmap lists and filters include [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
Best Rust community servers and Vanilla Rust servers, busiest first are the Rust Heatmap lists that [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 fits. These are the filters that return it on the list: Region: South America; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
What do the server tags on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 mean?
The game's server browser reads the tags [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 publishes: gmrust (Game mode): Rust survival, standard rules; mp487 (Max players): Slot count: 487; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): To join, run the same version: game protocol 2634; cs167781 (Build): Build 167781; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^b (Biweekly): The wipe interval is two weeks; ^v (Vanilla): Unchanged rates, kits and rules: the game in Facepunch's own form; SA (South America): In the server browser it sits under South America. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Who runs [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
One operator most likely runs [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10 and the 87 other servers we track that publish a eyhe.org hostname.
Connect
How do I join [LATAM] WeWert Server VANILLA | Biweekly | WIPE 15/10?
Enter client.connect 186.49.163.252:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.
