RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,217 Populated4,117 Fresh wipes 3 h156 Scan5 min
‹ All servers188.78.37.98:28015
Offline Full Queue Fresh wipe Wipe due No query

LaCosecha2027_Servidor1

Offline EU 188.78.37.98:28015 checked 20h ago

vanillamoddedcarbon
COM 1 · connect

Server instruments

last reading Mon 22:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg
0 10 30 60 120 256 FPS 239 SERVER FPS

Server fps

48 h low 105 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 10,000 ×1000

Entities

48 h range 10,000–11,000 · memory 1,770 MB
1239 ET SINCE RESTART 03:30

Uptime

3 h 30 min since its last restart, at the last reading
7-day average0peak –
Rank#15,369top 70% · #2582 in EU
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory1,770MBat the last reading
REC 1

Players

AveragePeakWipe
0123419:0000:0006:0011:0017:0022:00Wiped Mon 26 Oct, 16:09 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040019:0000:0006:0011:0017:0022:00Wiped Mon 26 Oct, 16:09 UTCWIPE

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% of all ranked servers, top 88% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap16 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctThu 24 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 16:09 UTC1d ago – – running 0
Fri 2 Oct, 15:42 UTC25d ago 2 halved by day 1 24 days 1
Thu 24 Sep, 15:39 UTC33d ago 0 – 8 days 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on LaCosecha2027_Servidor1 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.

How often does LaCosecha2027_Servidor1 wipe, and when?

There is no next wipe to predict: LaCosecha2027_Servidor1 wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 24 hours ago the current world was made.

Tag meanings

How should you read the tags on LaCosecha2027_Servidor1?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs169170 (Build): Build 169170; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon; EU (Europe): Its browser listing: Europe from LaCosecha2027_Servidor1. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show LaCosecha2027_Servidor1?

On Rust Metrics, LaCosecha2027_Servidor1 sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does LaCosecha2027_Servidor1 sit in the rankings?

Player hours over the last seven days put LaCosecha2027_Servidor1 at #15,369, #2,582 in Europe, in the top 70% of all ranked servers.

What player count does LaCosecha2027_Servidor1 carry?

LaCosecha2027_Servidor1 is not responding; status offline, last seen 20 hours ago. Check: player average. 0 over the last seven days.

Operator and location

Where does LaCosecha2027_Servidor1 sit?

Reading: location. The EU tag puts LaCosecha2027_Servidor1 in Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 188.78.37.98:28015.

What Rust version is LaCosecha2027_Servidor1 on?

Version check: Rust network protocol 2635 and build 169170 on Linux, run by LaCosecha2027_Servidor1. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on LaCosecha2027_Servidor1 within range?

Over the last 48 hours the average was 232 server fps; the floor was 105. Check: entities. The peak was 11,000, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 2,201 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is LaCosecha2027_Servidor1 up, and how often does it stay up?

Check: connection. LaCosecha2027_Servidor1 is offline at this moment. Last contact was 20 hours ago. By its reported uptime, the last restart was roughly 3 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on LaCosecha2027_Servidor1?

No gather rate appears in the name: LaCosecha2027_Servidor1. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on LaCosecha2027_Servidor1?

Size 6,000 and seed 1337: the game generates the procedural map on LaCosecha2027_Servidor1 from them. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

How to join

How do you connect to LaCosecha2027_Servidor1?

Press F1 in Rust and enter client.connect 188.78.37.98:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,^z,^y,^v,EU,gmvanilla,cs169170,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp0
Max players The server holds 0 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs169170
Build Build 169170.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

Region

EU
Europe Its browser listing: Europe.

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.