Working its way up from the back of the class: #12,801 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
38/ 100
F
Slipped a little: down 3,173 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 53% of all ranked servers, top 80% 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 2d 16h.
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 18/9?
You'll see [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 listed in South America, tagged SA. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 167.60.176.120:28015.
How reliable is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9, and is it up?
At this moment, [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 is offline; the last time it was seen was 29 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 28 September 2026, Rust Server Score saw it for the first time.
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. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 wipe its map?
biweekly: 14 days after its last wipe gives the basis for estimating [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9's next wipe. Friday 30 October at 23:31 UTC is the date set for its next wipe. 39 days 7 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
Player numbers
Where does [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 place in the wider field of Rust servers?
In South America, [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 is #197, and overall it is #12,801 on player hours over the last seven days, in the top 53% of all ranked servers.
Is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 a busy server?
It has been 29 days 10 hours since [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 was last seen, and it is offline right now.
Tags
What do [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9's tags stand for?
You'll see [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp487 (Max players): Its slot count is 487; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; SA (South America): The server browser lists it under South America in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who operates [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
The same operator most likely runs [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 and the 84 other servers we track that also publish a eyhe.org hostname.
Which Rust Server Score filters and lists feature [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
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. 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.
Rules and settings
How is [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 set up, and what rules does it keep?
You will find no gather rate in the name of [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is 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 18/9 runs which map?
A procedural map of size 4,000 and seed 2147483647, generated by the game, is what [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to [LATAM] WeWert Server VANILLA | Biweekly | WIPE 18/9?
To connect, start Rust, press F1, and type client.connect 167.60.176.120:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp487,ptrak,$r?,v2633,^b,^v,SA,gmrust,cs164530,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp487
Max playersIts slot count is 487.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
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. Even marks across the subjects, from F to D.