Working its way up from the back of the class: #13,322 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
22/ 100
F
Lost ground: down 7,405 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers, top 81% in SA. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Friday 30 October, 23:31 UTC, in 1d 5h.
Biweekly: 14 days after its last wipe
Wipes
newest first
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 sit?
The SA tag on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 puts it in South America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 190.133.47.54:28015.
Is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 up, and how steady is its uptime?
You cannot join now: [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 is offline, last seen 35 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 23 September 2026.
On what Rust version does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 sit?
Rust network protocol 2633 and build 164530 on Linux is what [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 reset?
The estimate for [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9's next wipe comes from biweekly: 14 days after its last wipe. Friday 30 October at 23:31 UTC is the date set for its next wipe. It has been running its current world for 40 days 18 hours. A fortnightly wipe schedule appears in its tags.
Player numbers
What position does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 hold in the rankings?
Over the last seven days, [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 has #13,322 for player hours, in the top 61% of all ranked servers and #199 in South America.
How many players does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 usually have?
[LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 is offline at the moment; the last time it was seen was 35 days 9 hours ago.
Tags
How should you read the tags on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
gmrust (Game mode): Rust survival, played by the standard rules; mp487 (Max players): The server holds 487 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; SA (South America): The server browser lists it under South America are the tags [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which person or group runs [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
87 other servers we track also use a eyhe.org hostname, so they and [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 most likely share an operator.
Where does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 among them: Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Map and rules
Which rules does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 enforce, and what are its settings?
The name of [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 uses?
The game generates the procedural map on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 at size 4,000 with seed 2147483647. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
Enter client.connect 190.133.47.54:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp487,ptrak,$r?,v2633,^b,^v,SA,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp487
Max playersThe server holds 487 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Region
SA
South AmericaThe server browser lists it under South America.
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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).