Working its way up from the back of the class: #15,108 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
52/ 100
D
Moving up: up 681 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
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.
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.
This server has not answered a direct query in the last 30 days.
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.
This server has not answered a direct query in the last 60 days.
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.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
BUNDANG_LOCAL_TILEFIX leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 112.149.91.140:28035.
How reliable is BUNDANG_LOCAL_TILEFIX, and is it up?
The server is down: BUNDANG_LOCAL_TILEFIX is offline now, with the last sighting 11 days 13 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
What Rust version is BUNDANG_LOCAL_TILEFIX on?
The server BUNDANG_LOCAL_TILEFIX is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does BUNDANG_LOCAL_TILEFIX reset?
There are too few wipes on record for BUNDANG_LOCAL_TILEFIX to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 12 days 12 hours.
Player numbers
What position does BUNDANG_LOCAL_TILEFIX hold in the rankings?
Over the last seven days, BUNDANG_LOCAL_TILEFIX has #15,108 for player hours, in the top 70% of all ranked servers.
How many players does BUNDANG_LOCAL_TILEFIX usually have?
It has been 11 days 13 hours since BUNDANG_LOCAL_TILEFIX was last seen, and it is offline right now.
Lists and filters
How should you read the tags on BUNDANG_LOCAL_TILEFIX?
The game's browser takes its cue from the tags BUNDANG_LOCAL_TILEFIX has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show BUNDANG_LOCAL_TILEFIX?
Rust Server Score lists that include BUNDANG_LOCAL_TILEFIX: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is BUNDANG_LOCAL_TILEFIX set up, and what rules does it keep?
Nothing in the name of BUNDANG_LOCAL_TILEFIX states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto BUNDANG_LOCAL_TILEFIX?
Enter client.connect 112.149.91.140:28035 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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. Strongest in momentum (D); standing is the one to work on (F).