Offline 89.179.241.141:28015 checked 20d ago
LAG-TEAM
Connect
srv = rust.server("89.179.241.141:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 18:11 UTC26d ago | 1 | NaN | running | 0 |
| 1 | Sun 20 Sep, 16:59 UTC38d 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.
display(srv.map, srv.info())Map
3700 · seed 420830277
- map
- Procedural Map
- size
- 3700
- seed
- 420830277
Server
srv.info()- address
- 89.179.241.141:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 19:09 UTC
- hostname
- ://l2lag.ru
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 176/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 125/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 19/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 288 on average | 14/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 18/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 23/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does LAG-TEAM rank?
Rank #15,825 on seven-day player hours for LAG-TEAM, within the top 72% of all ranked servers.
How many players does LAG-TEAM hold at once?
LAG-TEAM returns no live count at this refresh, having last been seen 20 days 3 hours ago.
About the server
What is the Rust version on LAG-TEAM?
Rust network protocol 2634 and build 166652 on Windows is what LAG-TEAM runs. The protocol has to match before you can join, and Steam does the updating.
Is LAG-TEAM up, and what does its uptime show?
Offline now for LAG-TEAM, last seen 20 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
In which location is LAG-TEAM hosted?
There is no region published for LAG-TEAM. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 89.179.241.141:28015 is its address.
Rules, settings, map
Which rules apply on LAG-TEAM, and what settings?
No gather rate appears in the name: LAG-TEAM. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has LAG-TEAM loaded?
Size 3,700, seed 420830277: the procedural map on LAG-TEAM, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does LAG-TEAM wipe, and how often?
Too few wipes are on record for LAG-TEAM to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 7 hours ago.
On LAG-TEAM, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 5.
Lists and tags
Where does LAG-TEAM appear among Rust Data lists and filters?
On Rust Data, LAG-TEAM appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on LAG-TEAM hold?
These tags are published by LAG-TEAM and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join LAG-TEAM?
The manual route: launch Rust, F1, then client.connect 89.179.241.141:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.