Channel
@Eintracht_Braunschweig
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
144subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001997474250 |
|---|---|
| Type | Channel |
| Username | @Eintracht_Braunschweig |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/Eintracht_Braunschweig |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 12 Sept 2026, 05:36 | 144 | -1 |
| 3 Sept 2026, 20:41 | 145 | +2 |
| 26 Aug 2026, 17:17 | 143 | +1 |
| 19 Aug 2026, 13:47 | 142 | +6 |
| 13 Aug 2026, 03:34 | 136 | +3 |
| 9 Aug 2026, 00:16 | 133 | no change |
| 6 Aug 2026, 23:08 | 133 | +1 |
| 6 Aug 2026, 10:54 | 132 | first reading |
20 posts held, back to 8 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
36 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 66.7% | |
| 🔥 | 5 | 13.9% | |
| 🥰 | 4 | 11.1% | |
| 😁 | 2 | 5.56% | |
| 👍 | 1 | 2.78% |
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 10 of the 20 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 August 2026 to 8 August 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.
🗣 Ларс Корнетка: «Я очень рад, что матч сложился для нас таким образом. Мы тщательно готовились к сильному сопернику. Нам хорошо удалось нейтрализовать сильные стороны Магдебурга при игре с мячом. И мы сразу же смогли вознаградить себя за это контратакой. Затем мы вошли в игровой поток и смогли жестко воспользоваться потерей концентрации соперника. С таким импульсом игра, конечно, склоняется в одну сторону, поэтому…
❤3👍1
🗣 Ян Урбих: «Во время матча ты настолько погружен в игру, что вообще не думаешь о моментах или голах. Ты просто концентрируешься на том, чтобы следовать плану на игру. Если бы кто‑нибудь перед матчем сказал мне, что я внесу вклад в победу двумя забитыми голами, я бы, конечно, сразу согласился на это».
❤3
🗣 Рон-Торбен Хоффманн: «Сегодня мы наглядно показали тот голод и ту жажду борьбы, которые хотим олицетворять. То, что мы забили шесть голов, — это, конечно, безумие. Тем не менее нам определенно еще есть что улучшить, особенно в организации обороны. Но сегодняшнюю победу точно можно и нужно отпраздновать. Макс и Саму провели отличный матч. Вместе они буквально намотали огромное количество километров и неуступчиво и…
❤3
🙂 Заканчивайте сезон
❤3😁2
❤️ Эмоции после первой победы в сезоне!
🥰4
✍️ Оценки игроков по итогам матча с Магдебургом (WhoScored) ☺️ Ян Урбих признан лучшим игроком встречи!
❤4
😍 Дебюта сезона лучше не придумаешь! 2️⃣ Магдебург – Айнтрахт Брауншвейг – 1:6 ⚽ Голы: Опоку 0:1 (16'), Урбих 0:2 (21'), Урбих 0:3 (26'), Айдын 0:4 (пен., 44'), Жуковский 1:4 (49'), Ди Бенедетто 1:5 (50'), Флик 1:6 (61') 🟥 Удаление: Бокхорн (Магдебург, 31')
❤6🔥3
Отличный момент был у Сане, чтобы забить еще один, но не смог попасть в ближний угол Сиди из убойной позиции 90+2'
Вагнер заменил Флика 86'
Каттербах и Сане также появились на поле – Ди Микеле Санчез и Опоку заменены 78'
Зе вышел на ударную позицию и пробил в дальний угол, но голкипер Магдебурга выручил хозяев 72'
Двойная замена в стане Айнтрахта Гомес и Зе вышли на поле вместо Ди Бенедетто и Штурма 65'
Showing the 12 most recent of 20 posts we hold for @Eintracht_Braunschweig. 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.
Named by 12 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Айнтрахт Брауншвейг | Eintracht Braunschweig” (@Eintracht_Braunschweig), 144 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Eintracht_Braunschweig.
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.