Актив, ау...
custom 54474931911692502493
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB

Channel
@KaisersChannel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
64subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002276073878 |
|---|---|
| Type | Channel |
| Username | @KaisersChannel |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/KaisersChannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 21:39 | 64 | -1 |
| 21 Aug 2026, 16:36 | 65 | +1 |
| 13 Aug 2026, 23:31 | 64 | no change |
| 13 Aug 2026, 23:17 | 64 | first reading |
20 posts held, back to 24 June 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 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.
127 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5447493191169250249 | 41 | 32.3% | |
| custom 5447332031111397098 | 37 | 29.1% | |
| custom 5192814863310669616 | 17 | 13.4% | |
| custom 5388903201527329984 | 11 | 8.66% | |
| custom 5193119913362869566 | 9 | 7.09% | |
| custom 5355192462782528091 | 7 | 5.51% | |
| custom 5258474300402337334 | 4 | 3.15% | |
| custom 5388777921626274894 | 1 | 0.787% |
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 19 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 127 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 24 June 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.
Актив, ау...
custom 54474931911692502493
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Актив поднимаем
custom 54474931911692502497custom 53551924627825280911custom 54473320311113970981
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Реакции пожалуйста 🐶
custom 54474931911692502496
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Мне почему-то нравится😰
custom 54473320311113970986custom 54474931911692502492custom 53551924627825280911custom 53889032015273299841
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Отдать голос каналу можно здесь 👇 https://t.me/boost/KaisersChannel (Для реакций)
custom 53889032015273299843
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Реакции пожалуйста Тык
custom 54474931911692502497
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Анимашка подъехала
custom 54473320311113970988custom 51928148633106696163custom 53889032015273299843custom 53551924627825280911
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Гайс,у кого есть тгк, давайте вп? Мне нужны подписоты🌹🫶
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Почему на Тони больше реакций, чем на Джекете, он же чисто тру Адам
custom 54474931911692502491
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Чтоооооо, Джекет?? Да ну нафиг.. 😰
custom 51931199133628695668custom 51928148633106696166custom 54473320311113970983
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
#вп
custom 54473320311113970981
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
ᅠ📼 хочется стикерпаков/эмодзи с любимыми персонажами из hotline Miami ?? ᅠᅠᅠНету нигде аватарок с твоими любимыми персонажами ?? ︶︶ 🐺 :: Тогда ты в правильном месте !! ᅠᅠᅠᅠᅠᅠАдмины :: 🐺 :: Влд // отвечает за всё // он/его #Ртпост
custom 54473320311113970983
Signed Ꮁᴏᴄᴨᴏжᴀ Ꮶᴀйɜ #JB
Showing the 12 most recent of 20 posts we hold for @KaisersChannel. 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“ᴋᴀɪsᴇʀ's ᴄʜᴀɴɴᴇʟ” (@KaisersChannel), 64 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/KaisersChannel.
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.