Offline 76.104.183.243:28015 checked 26d ago
llamas_build
Connect
srv = rust.server("76.104.183.243: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. 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 60% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:57 UTC FW26d ago | 1 | NaN | running | 0 |
| 1 | Wed 16 Sep, 19:40 UTC41d ago | 1 | halved by day 9 | 15 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 76.104.183.243:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:57 UTC
- hostname
- –
- 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 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 117/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 117/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 47/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 24/1000 |
Quick answers
From the figures on this page.
Population
How does llamas_build compare in the rankings?
Player hours over seven days put llamas_build at #13,830, in the top 60% of the ranked set.
How full does llamas_build run?
llamas_build returns no live count at this refresh, having last been seen 26 days 3 hours ago.
About the server
What Rust version does llamas_build run?
Rust network protocol 2634 and build 166494 on Windows is what llamas_build runs. Joining needs the same protocol on your game; Steam handles the update.
Is llamas_build up, and what does its uptime show?
Offline now for llamas_build, last seen 26 days 3 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does llamas_build sit?
There is no region published for llamas_build. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 76.104.183.243:28015.
Settings and map
Which rules apply on llamas_build, and what settings?
The name llamas_build carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
On what schedule does llamas_build wipe?
A rhythm cannot be read from the wipes of llamas_build on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 26 days 12 hours ago.
On llamas_build, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 9.
Tags, lists
Where does llamas_build appear among Rust Data lists and filters?
The Rust Data lists that llamas_build fits are: Modded Rust servers and Servers with build or creative tags. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on llamas_build hold?
The game's server browser reads these tags from llamas_build: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): 4 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join llamas_build?
In Rust, F1 opens the console: type client.connect 76.104.183.243:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.