Working its way up from the back of the class: #13,504 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
41/ 100
F
Slipped a little: down 2,368 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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.
Average fpsLowest fpsWipe
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
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 11 Oct. 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 88% 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, 00:00 UTC, in 38m.
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
Where in the world is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10?
In South America, according to its own listing, sits [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10, with the SA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 186.55.18.133:28015.
How reliable is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10, and is it up?
The server is down: [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 is offline now, with the last sighting 18 days 3 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 11 October 2026.
On what Rust version does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 sit?
The server [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 is on Rust network protocol 2634 and build 166494 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 wipe, and how often?
biweekly: 14 days after its last wipe gives the basis for estimating [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10's next wipe. Expect the next wipe on Friday 30 October at 00:00 UTC. 27 days 23 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
Population
Where does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 place in the wider field of Rust servers?
In South America, [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 is #192, and overall it is #13,504 on player hours over the last seven days, in the top 61% of all ranked servers.
What does the population on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 look like?
[LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 is offline at the moment; the last time it was seen was 18 days 3 hours ago.
Lists and filters
What do [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp487 (Max players): Its slot count is 487; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; SA (South America): You will find it under South America in the browser are the tags [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which person or group runs [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10?
88 other servers we track also use a eyhe.org hostname, so they and [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 most likely share an operator.
Which lists and filters on Rust Server Score show [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10?
Rust Server Score lists that include [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10: Best community servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server 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.
Map and rules
What settings and rules apply on [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10?
You will find no gather rate in the name of [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
[LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 runs which map?
[LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10 runs a game-generated procedural map at size 4,000, seed 15565093. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto [LATAM] WeWert Server VANILLA | Biweekly | WIPE 1/10?
To connect, start Rust, press F1, and type client.connect 186.55.18.133:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp487,ptrak,$r?,v2634,^b,^v,SA,gmrust,cs166494,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp487
Max playersIts slot count is 487.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Region
SA
South AmericaYou will find it under South America in the browser.
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. Even marks across the subjects, from F to F.