Skip to the page
RUST ANALYTICS
LIVE80,906PLY11,704SRV
QUOTE 89.179.241.141:28015 Offline checked 5d ago

LAG-TEAM

Players · last
0/ 5
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 5
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#15,901
top 71%
Rank · 7d ago
#7,033
8868 places down
Last wipe
11d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
3700
Procedural Map · seed 420830277
First seen
13 Sep 2026
://l2lag.ru

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
12 days
between real wipes
wipe-day peak
1
players, last three wipes
crowd held
0%
else halves by day 5

The first 48 hours of its last wipes

Fri 2 OctSun 20 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 18:11 UTC11d ago 1 – running 0
Sun 20 Sep, 16:59 UTC23d ago 1 halved by day 5 12 days 1

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

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 399 on average560/600+9+1.7%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 343 on average436/475−31−6.6%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 334 on average180/200−22−10.8%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 325 on average364/375−64−14.9%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average44/250−36−45.2%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 275 on average330/400+14+4.3%

Quick answers

from the figures on this page

Rules & Settings

What settings and rules are in place on LAG-TEAM?

No gather rate appears in the name of LAG-TEAM. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. You will find it under Community in the server browser: it is a community server. VAC is active.

Which map is played on LAG-TEAM?

LAG-TEAM uses a procedural map of size 3,700 with seed 420830277, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Population

Where does LAG-TEAM sit in the rankings?

In the top 71% of all ranked servers, LAG-TEAM is #15,901 on player hours over the last seven days.

What is the population on LAG-TEAM?

Right now, LAG-TEAM is offline; the last sighting was 5 days 17 hours ago. Average players over the last seven days: 0.

Wipe Cycle

How does LAG-TEAM handle wipe day?

An average of 1 players marked the busiest point of its recent wipes. 1 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. The crowd fell below half by day 5 when it did not hold.

When does LAG-TEAM schedule its wipes?

There are too few wipes on record for LAG-TEAM to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 11 days 20 hours ago the current world was created.

Server Overview

What is the server location for LAG-TEAM?

For LAG-TEAM, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 89.179.241.141:28015 is its address.

What Rust version is LAG-TEAM running?

The version in use at LAG-TEAM: Rust network protocol 2634 and build 166652, on Windows. The protocol has to match for you to join, and Steam applies that update.

Is LAG-TEAM up, and how consistent is its uptime?

No response from LAG-TEAM. It was last seen 5 days 17 hours ago. The last 7 full days give 28% uptime, 47 hours on out of 168. First sighting by Rust Analytics: 13 September 2026.

Tags and Rankings

How should you interpret the tags on LAG-TEAM?

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp5 (Max players): Slot count: 5; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set, which LAG-TEAM publishes. Also in the tags and at the top of this page: current players, queue and world creation time.

LAG-TEAM appears in which of the lists and filters on Rust Analytics?

On Rust Analytics, LAG-TEAM matches these lists: Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Connection

What is the process to join LAG-TEAM?

Type client.connect 89.179.241.141:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust's standard survival mode.
mp5
Max players Slot count: 5.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol Protocol 2634: matching game versions are required to join.
cs166652
Build Game build: 166652.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code Region code: none set.

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.