Telegram RegisterThe public register of Telegram

Channel

Die Schwaben | Штутгарт

@Stuttgart1893

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

350subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001771926843
TypeChannel
Username@Stuttgart1893
DescriptionBoosty – https://boosty.to/stuttgart1893
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Stuttgart1893

Growth

3507 Aug 2026, 11:34 — 350 subscribers8 Aug 2026, 06:48 — 350 subscribers7 Aug 2026, 11:348 Aug 2026, 06:48
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 349–351 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:48350no change
7 Aug 2026, 11:34350first reading

Engagement

20 posts held, back to 12 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.9%
avg views ÷ 350 subscribers
Avg views / post
108
17 posts measured
Reaction rate
5.88%
reactions ÷ views · ER floor
Posts in window
17
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held20 (12 July 20261 August 2026)
Views total1,837
Reactions total108
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:48 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.

What this channel posts

Photos
791
Videos
93
Links
1,010

Lifetime counters from Telegram’s own channel header, read 8 August 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.

Video runtime
12s
Average length
12s

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.

Reaction mix

131 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 76.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10076.3%
1410.7%
💔75.34%
🥰43.05%
👀10.763%
👻10.763%
😢10.763%
😱10.763%
🤔10.763%
🤷‍♂10.763%

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 20 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 131reactions 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 12 July 2026 to 1 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.

Recent posts

1 Aug 2026, 16:15 UTC78 views5 reactionsread 8 August 2026

​​Играем вничью по итогам 105-минутного матча. Голы: 15' – ⚽️ Йованович (🅰️ Фюрих) – 1:0 55' – ⚽️ Загаду (🅰️ Фюрих) – 2:0 71' – ⚽️ Колеошо (–) – 2:1 105' – ⚽️ Колеошо (–) – 2:2 💡Матч получился интересным. На протяжении первого часа «Штутгарт» доминировал в игре, но во втором команда сыграла хуже. Рад возвращению на поле Хендрикса и Шабо, которые восстановились после повреждений. Если говорить о персоналиях, кто при

👍5

1 Aug 2026, 12:28 UTC75 views4 reactionsread 8 August 2026
Photo

Стартовый состав на товарищеский матч против «ФК Париж»: Бредлоу – Макси, Загаду, Ельч, Нарти – Шпальт, Чема – Фюрих, Томаш, Йованович – Милошевич 🪑На скамейке запасных: Функ (В), Дрляча (В), Аль-Дахиль, Шабо, Хендрикс, Стергиу, Вагноман, Оливье, Катович, Ульрих, Йигит, Люерс, Маланга, Буанани, Цингас, Рельке, Ван дер Лей.

👍4

1 Aug 2026, 10:26 UTC77 views5 reactionsread 8 August 2026
Photo

⚪️ Matchday 🔴 ⚽️ «Штутгарт» – «ФК Париж» 🏆 Товарищеский матч 🕖 16:00 МСК 🎥 VfB-TV

3👍2

29 Jul 2026, 19:25 UTC90 views5 reactionsread 8 August 2026

​​Уверенная игра в Оффенбахе. 6' – ⚽️ Оливье (–) – 0:1 10' – ⚽️ Фюрих (–) – 0:2 17' – ⚽️ Томаш (🅰️ Фюрих) – 0:3 41' – ⚽️ Бенедикт (🅰️ Пистритто) – 1:3 45+1' – ⚽️ Ульрих (🅰️ Ельч) – 1:4 52' – ⚽️ Йованович (🅰️ Аль-Дахиль) – 1:5 62' – ⚽️ Шпальт (🅰️ Вагноман) – 1:6 75' – ⚽️ Йованович (🅰️ Милошевич) – 1:7 89' – ⚽️ Милошевич (🅰️ Йованович) – 1:8 💡Счёт, конечно, о многом говорит с точки зрения игры. Матч получился интенси

👍5

29 Jul 2026, 17:37 UTC83 views9 reactionsread 8 August 2026

​​📝 Официально: Лео Сауэр переходит в «Штутгарт» из «Фейеноорда» и подписывает контракт до 2031 года. 📜 20-летний вингер начал свою футбольную карьеру в родном словацком городе - в братиславском «Словане». Затем он прошёл через все юношеские команды «МСК Жилина». Летом 2022 года, в 16 лет, он переехал в Нидерланды, присоединившись к «Фейеноорду». Сначала играл за «U21», а уже 20 августа 2023 года дебютировал в Эреди

5🥰4

29 Jul 2026, 16:25 UTC78 views4 reactionsread 8 August 2026
Photo

Стартовый состав на товарищеский матч против «Оффенбаха»: Бредлоу – Макси, Загаду, Ельч, Оливье – Премель, Чема – Фюрих, Ульрих, Буанани – Томаш 🪑На скамейке запасных: Функ (В), Аль-Дахиль, Херверт, Вагноман, Шпальт, Йигит, Штанге, Пенна, Маланга, Йованович, Рельке, Майхжак, Милошевич. ❗️Начало матча из-за задержки прибытия нашей команды перенесено на 19:45.

👍4

29 Jul 2026, 09:00 UTC86 views5 reactionsread 8 August 2026
Photo

⚪️ Matchday 🔴 ⚽️ «Оффенбах» – «Штутгарт» 🏆 Товарищеский матч 🕖 19:30 МСК 🏟 Stadion am Bieberer Berg 🎥 Sky Sports

👍5

28 Jul 2026, 14:48 UTC104 views10 reactionsread 8 August 2026

​​«Штутгарт» представил гостевую форму на сезон 2026/27! 📜 Археологические раскопки по всему Баден-Вюртембергу принесли множество находок. Это относится и к Бад-Канштатту: как можно наблюдать и сегодня на окраине Канштаттского курортного парка, здесь сохранилось особенно много следов римской эпохи. Однако уже в середине первого тысячелетия до нашей эры на этих землях, как доподлинно известно, селились и племена, кот

👍81🤔1

27 Jul 2026, 17:47 UTC106 views7 reactionsread 8 August 2026

​​«Штутгарт» усиливает атаку? 📑 Усиление атакующей линии было одной из целей этого трансферного окна. Главные кандидаты уже известны, а с одним из них всё решено. ♦️ Начнём с позиции форварда, где «Штутгарт» уже пару недель торгуется с «Вольфсбургом» по поводу Дженана Пейчиновича. «VfB» сделал предложение за 21-летнего немецкого нападающего - 18 миллионов евро с учётом бонусов, но оно было отклонено. «Вольфсбург» х

👍6🤷‍♂1

27 Jul 2026, 13:50 UTC94 views7 reactionsread 8 August 2026
Video

👀 Завтра, видимо, представят третью и гостевую форму на предстоящий сезон! 🤔 Неужели в этом сезоне обойдутся без красной гостевой формы?

👍7

25 Jul 2026, 15:32 UTC112 views5 reactionsread 8 August 2026

​​Непростой товарищеский матч в Холленбахе. Голы: 24' – ⚽️ Томаш (🅰 Фюрих) – 0:1 41' – ⚽️ Фюрих (–) – 0:2 50' – ⚽️ Макси (🅰 Шпальт) – 0:3 59' – ⚽️ Милошевич (🅰 Пенна) – 0:4 63' – ⚽️ Нарти (🅰 Маланга) – 0:5 💡 Первый тайм расстроил: в атаке, кроме индивидуальных попыток Фюриха, комбинаций Премеля и Ульриха и дальних ударов Оливье, больше ничего не было. Буанани абсолютно провалил матч - замедлял темп атаки и в некото

👍5

25 Jul 2026, 12:20 UTC104 views4 reactionsread 8 August 2026
Photo

Стартовый состав на товарищеский матч против «Холленбаха»: Бредлоу – Вагноман, Загаду, Аль-Дахиль, Оливье – Йигит, Премель – Фюрих, Томаш, Буанани – Милошевич 🪑На скамейке запасных: Функ (В), Ельч, Херверт, Макси, Шпальт, Чема, Ульрих, Нарти, Пенна, Йованович, Маланга, Рëльке ❗️Ульрих на поле, но вместо кого, не ясно.

👍4

Showing the 12 most recent of 20 posts we hold for @Stuttgart1893. 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.

Citation-graph rank

Citation-graph rank — 88,066 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 9 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.

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.

Cite this entry

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Die Schwaben | Штутгарт” (@Stuttgart1893), 350 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Stuttgart1893.

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.