Channel
@a_jager
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
173subscribers
+9 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002449604138 |
|---|---|
| Type | Channel |
| Username | @a_jager |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/a_jager |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 20:19 | 173 | +1 |
| 31 Aug 2026, 00:55 | 172 | +6 |
| 24 Aug 2026, 16:16 | 166 | +2 |
| 15 Aug 2026, 02:45 | 164 | no change |
| 15 Aug 2026, 02:32 | 164 | first reading |
11 posts held, back to 18 July 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 11 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
348 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 27.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235707142622704016 | 96 | 27.6% | |
| custom 5285031942914351486 | 80 | 23.0% | |
| custom 5449439429829635331 | 54 | 15.5% | |
| custom 5406867894380296399 | 35 | 10.1% | |
| custom 5415665988857264819 | 28 | 8.05% | |
| custom 5273886906508133889 | 25 | 7.18% | |
| custom 5470060439696067341 | 19 | 5.46% | |
| custom 5298826652019626573 | 9 | 2.59% | |
| custom 5406643044252418462 | 2 | 0.575% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 11 of the 11 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 348 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 18 July 2026 to 11 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.
😺Klaus Jäger VS Hans von Schneider😺 Всё новое — хорошо забытое старое #Pictures #Т34 #7разбойников #KlausJäger #HansvonSchneider
custom 527388690650813388922custom 54494394298296353316custom 52357071426227040165custom 54066430442524184622
Полный трейлер «7 Қарақшы/7 разбойников»!💥 И мы наконец-то видим нашего главного героя во всей красе. Держали самое сладное на последок🤩 #Films #7разбойников
custom 544943942982963533120custom 52357071426227040164custom 54156659888572648193
Трейлер-тизер «7 қарақшы/7 разбойников» до и после монтажа💥 #Films #7разбойников
custom 541566598885726481918custom 52357071426227040166custom 54494394298296353316
Ну раз создатели решили выпускать одни и те же кадры в разных обработках, то чем я хуже, чтобы ими не делиться?❤️ В любом случае, Винценца много не бывает💥 #Pictures #Films #7разбойников #HansvonSchneider
custom 544943942982963533122custom 52357071426227040165custom 52988266520196265734
Персональные кадры-постеры тоже появились💥 Официальное знакомство с Гансом состоялось! 💥 #Films #Pictures #7разбойников #HansvonSchneider
custom 528503194291435148624custom 54068678943802963995custom 54700604396960673415
Создатели «7 қарақшы/7 разбойников» опубликовали трейлер-тизер❤️ И мы наконец-то получили первый кадр с Гансом! Ура!😺 #Films #7разбойников
custom 528503194291435148619custom 52357071426227040165custom 54068678943802963993custom 54700604396960673412
Новая порция закулисных кадров со съёмочной площадки «7-қарақшы». Мне удалось найти ещё несколько фотографий Винценца Кифера со съёмок фильма.❤️ Так что делюсь находками с вами. Рассматриваем детали и любуемся образом Ганса фон Шнайдера. Источники: aibekmma mukhtarkapalbayev ⟣Tags:: #VinzenzKiefer #7Разбойников #ГансфонШнайдер
custom 523570714262270401621custom 52850319429143514867custom 54068678943802963996
Трагедия в трех актах об отсутствии Винценца на постере и в трейлере-тизере✨ #Memes #7разбойников
custom 523570714262270401623custom 54700604396960673415custom 52850319429143514864custom 52738869065081338892
А вы знали, что мотоцикл Алекса Брандта сейчас ездит где-то по российским дорогам?🤩 Да, новость уже далеко не свежая. Когда-то я не стала её выкладывать, потому что подумала: «Ну, не настолько это интересно». Но сегодня мне вполне справедливо прилетело: «Блин, а почему ты об этом не рассказала?». Так что исправляюсь😊 Делюсь с вами небольшим рассказом о том, как эта настоящая реликвия попала в Россию — со слов …
custom 540686789438029639921custom 54700604396960673416custom 54156659888572648193custom 52357071426227040162custom 52738869065081338891
Вчера был представлен официальный постер 7 разбойников («7 қарақшы») . Но, признаюсь честно, мне всё-таки не хватило на нём одного очень важного человека. 👀 Поэтому я решила немного пофантазировать и сделать собственные версии постера — с Винценцом Кифером. И знаете... мне они нравятся гораздо больше. Оригинал оставлю в комментариях. ⟣Tags:: #VinzenzKiefer #7Разбойников #𝘢𝘳𝘵
custom 528503194291435148622custom 52357071426227040166custom 54156659888572648194custom 54700604396960673411
4:19 a_jager исправляет титры в фильме, потому что русские не умеют правильно писать имя Винца 4:20 deuzw делает собственные постеры, потому что казахи не знают, кто у них главная звезда экрана А если без шуток, просто оцените красоту моей коллеги по фандому. Да, это самодельные постеры, официальный выглядит по другому❤️ #7разбойников
custom 523570714262270401619custom 52988266520196265735custom 52850319429143514864
Showing the 11 most recent of 11 posts we hold for @a_jager. 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 1 registered channel — 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“KLAUStrophobia♣︎” (@a_jager), 173 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/a_jager.
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.