⭐️🇩🇪 بعد از حضور در هر سه بازی ابتدایی، سرژ گنابری اردوی تیم ملی آلمان رو ترک کرده و در بازی مقابل یونان حضور نخواهد داشت. ❌ 🔻 #Harry 🔴 @BayernMuncheni
❤3

Channel
@BayernMuncheni
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
41,184subscribers
+20,368 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001071963256 |
|---|---|
| Type | Channel |
| Username | @BayernMuncheni |
| Description | 🔴Mia san mia🔴 🔘اولین و بزرگترین مجموعه هواداری باشگاه بایرن مونیخ در ایران 🏁 بازی بعدی 🏆 هفته 5 بوندسلیگا آگزبورگ 🆚 بایرن 📍 و.و.ک. آرهنا 📅 شنبه، 18 مهر ⏰ 17:00 💎تبلیغات | @GrowAdsTeam |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/BayernMuncheni |
Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 14:02 | 41,184 | +112 |
| 17 Sept 2026, 16:16 | 41,072 | -7 |
| 15 Sept 2026, 12:16 | 41,079 | +10 |
| 13 Sept 2026, 17:57 | 41,069 | +30 |
| 12 Sept 2026, 01:55 | 41,039 | +86 |
| 9 Sept 2026, 15:39 | 40,953 | +12 |
| 6 Sept 2026, 05:58 | 40,941 | +16 |
| 3 Sept 2026, 22:36 | 40,925 | +25 |
| 2 Sept 2026, 16:42 | 40,900 | +9 |
| 1 Sept 2026, 16:57 | 40,891 | +8 |
| 31 Aug 2026, 19:48 | 40,883 | +8,005 |
| 30 Aug 2026, 17:07 | 32,878 | +12,003 |
| 29 Aug 2026, 16:57 | 20,875 | +4 |
| 28 Aug 2026, 20:23 | 20,871 | +17 |
| 27 Aug 2026, 21:23 | 20,854 | +19 |
| 27 Aug 2026, 00:44 | 20,835 | +24 |
| 26 Aug 2026, 01:53 | 20,811 | -4 |
| 25 Aug 2026, 04:37 | 20,815 | +2 |
| 23 Aug 2026, 23:02 | 20,813 | +55 |
| 22 Aug 2026, 05:36 | 20,758 | first reading |
1,215 posts held, back to 10 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 112 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 574 of 666 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 October 2026 |
|---|---|
| Posts held | 1,215 (10 August 2026 – 2 October 2026) |
| Views total | 695,633 |
| Reactions total | 23,939 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 19:09 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
37,037 reactions across 859 posts, in 30 distinct kinds. The most used accounts for 59.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22,121 | 59.7% | |
| 🔥 | 4,545 | 12.3% | |
| 👍 | 2,825 | 7.63% | |
| 🤣 | 2,186 | 5.90% | |
| 💔 | 1,750 | 4.73% | |
| ❤🔥 | 798 | 2.15% | |
| 🖕 | 507 | 1.37% | |
| 👎 | 506 | 1.37% | |
| 😐 | 364 | 0.983% | |
| 👏 | 356 | 0.961% | |
| 🤡 | 289 | 0.78% | |
| 🤬 | 142 | 0.383% | |
| 🗿 | 130 | 0.351% | |
| 😍 | 98 | 0.265% | |
| 🏆 | 81 | 0.219% | |
| 🤔 | 75 | 0.203% | |
| 🍾 | 61 | 0.165% | |
| 💘 | 41 | 0.111% | |
| 😢 | 39 | 0.105% | |
| 😱 | 36 | 0.097% | |
| 10 further kinds | 87 | 0.235% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 865 of the 1,000 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 37,037 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 20 August 2026 to 2 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @BayernMuncheni. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 20 August 2026 to 2 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
⭐️🇩🇪 بعد از حضور در هر سه بازی ابتدایی، سرژ گنابری اردوی تیم ملی آلمان رو ترک کرده و در بازی مقابل یونان حضور نخواهد داشت. ❌ 🔻 #Harry 🔴 @BayernMuncheni
❤3
🇮🇹پیشبینی شما از دیدار حساس ایتالیا و فرانسه🇫🇷
🖕2
🇪🇺🇫🇷 حضور اوپامکانو و اولیسه در ترکیب اصلی فرانسه مقابل ایتالیا. 🔻 #Harry 🔴 @BayernMuncheni
❤13🔥2
🇩🇪🔻 بایرن بند بازخرید موریس کراتنماخر رو به ارزش 7.5 میلیون یورو در اختیار داره. ✅ 🇩🇪 قرارداد این بازیکن با الفرسبرگ تا 2030 اعتبار داره و بند آزادسازیش 9 میلیون یوروئه. 🔗 [Christian Falk, #Bild 📰] 🔻 #Harry 🔴 @BayernMuncheni
❤27
🇩🇪⭐️ تیم منتخب ارزشمندترین بازیکنان بوندسلیگا در اکتبر 2026. 🔻 #Harry 🔴 @BayernMuncheni
❤25
🌍 دوستانه ملی 🇰🇷 کره جنوبی 0-0 ونزوئلا 🇻🇪 ⭐️کیم مین جائه: 80 دقیقه 🔻 #Harry 🔴 @BayernMuncheni
🤣24❤6
🚑🇬🇷 به گزارش منابع یونانی، کریستوس زولیس، وینگر آرسنال نمیتونه تیم ملی کشورش رو در بازی یکشنبه مقابل آلمان همراهی کنه. ❌ 🔻 #Harry 🔴 @BayernMuncheni
❤16
❤️ سایت جهانی WinWin Bet ❤️ 😀😃😄 😀😃😄 🎁 بازگشت باخت به صورت هفتگی ✅ پرداخت جوایز سریع و امن 🫶 شارژ حساب از طریق ارز دیجیتال و انواع ووچر ┅━━━━━━━━━━━ 🎁 کد هدیه ثبت نام: Win7 🫶 ثبت نام کنید. 👇 📱 نصب اپلیکیشن اندروید کلیک کنید 💳 آموزش شارژ با کارت بانکی 💸آموزش شارژ با یو ووچر 💰آموزش شارژ با ارز دیجیتال 💵 آموزش شارژ با پرمیوم ووچر 🔗 لینک ورود به سایت : 📱winwin.link 📱winwin.link 📱winwin.link 💪لین…
📲 اپلیکیشن اندروید سایت وین وین بت 🔥 💳 آموزش شارژ با کارت بانکی 💸آموزش شارژ با یو ووچر 💰آموزش شارژ با ارز دیجیتال 💵 آموزش شارژ با پرمیوم ووچر
🇩🇪🔻 خیویرو رید همچنان مدنظر مدیران بایرن قرار دارد. اینکه بایرن تابستان برای جذب او اقدامی نکرد، به این دلیل نبود که مدیران باشگاه نسبت به او متقاعد نشده بودند؛ بلکه نتوانستند ساشا بویی را به تیم دیگری منتقل کنند. 🔴 برای آینده، بایرن همچنان این مدافع هلندی را میپسندد و اگر بتوانند بویی را به باشگاه دیگری واگذار کنند، احتمال اقدام برای جذب رید وجود دارد؛ هرچند چند باشگاه لیگ برتری هم به دنبال جذب او هستند. 🔗 [Chris…
❤26
🎤🔻 ایجنت دنی اولمو، اندی بارا، فاش کرد که بایرن مونیخ دو بار برای جذب موکلش اقدام کرده؛ یک بار زمانی که در دینامو زاگرب بود و بار دیگر در لایپزیش: «وقتی هنوز در دینامو بود، به پیشنهاد خودم پیشنهاد بایرن را رد کردیم. بهش گفتم: "تو به یک مرحله دیگه نیاز داری." همین اتفاق هم افتاد. بعدتر، زمانی که بازیکن لایپزیش بود، دوباره یک پیشنهاد از بایرن دریافت کرد.» 🔗 [Podcast Inkubator via #GOAL 📰] 🔻 #Harry 🔴 @BayernMuncheni
❤17👎4
💭🇩🇪 یورگن کلوپ حاضر نشد وارد بحث درباره این موضوع شود که آیا یوشوا کیمیش هنوز بازیکنی غیرقابلجایگزین است یا نه؛ آن هم بعد از اینکه خط میانی پاولوویچ، بیشوف و ویرتز مقابل صربستان عملکرد خوبی داشت. ⁉️ سؤال خبرنگار در واقع یک اشاره غیرمستقیم بود: «اینکه پاولوویچ و بیشوف کنار فلو ویرتز بازی میکردند، چقدر کار را برای او راحتتر کرد؟ و آیا درک متقابل بین آنها همین حالا هم خیلی به چیزی که شما ایدهآل میدانید نزدیک شده؟…
❤20👍5
Showing the 12 most recent of 1,215 posts we hold for @BayernMuncheni. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
@BayernMuncheni named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 31 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 27 September 2026 — this entry's latest reading, not the date you are reading this.
“بایرن مونیخ | Bayern Munich” (@BayernMuncheni), 41,184 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/BayernMuncheni.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.