Channel
@kaisaedaily
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
202subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001711887771 |
|---|---|
| Type | Channel |
| Username | @kaisaedaily |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/kaisaedaily |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 08:47 | 202 | +12 |
| 7 Aug 2026, 07:15 | 190 | no change |
| 6 Aug 2026, 21:46 | 190 | first reading |
19 posts held, back to 24 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 pageof 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 13 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (24 July 2026 – 7 August 2026) |
| Views total | 1,354 |
| Reactions total | 225 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 07:15 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.
225 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5445186037817053824 | 48 | 21.3% | |
| custom 5389054358606353281 | 41 | 18.2% | |
| custom 5415904862053366725 | 40 | 17.8% | |
| custom 5240124915918594794 | 36 | 16.0% | |
| custom 5445078569145370956 | 22 | 9.78% | |
| custom 5445267298598293850 | 20 | 8.89% | |
| custom 5251399248020267972 | 9 | 4.00% | |
| custom 5447515941611014713 | 9 | 4.00% |
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 areTelegram’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 13 of the 19 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 225reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 July 2026 to 7 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.
🗝⎯ׅ⎯ׄ 𝅥 𝅥 🤩𝓹 𝓬𝓸𝓷︭𝓯︭𝓮𝓼𝓼︭𝓲𝓸𝓷 🥹🤩⎯ׄ 𔖳 𝘰𝘸𝘯 : @𝘑𝘶𝘴𝘵𝘚𝘢𝘯𝘥𝘢.. 🌟 𖥻 𝖲𝗎𝖻𝗌𝖼︭𝗋𝗂𝖻𝖾 𝗍𝗈 𝗍𝗁𝖾 𝖼𝗁𝐚𝗇𝗇𝖾𝗅 𝗐𝗁𝖾𝗋︭𝖾︭𝗏︭𝖾𝗋 𝗉𝗈𝗌𝗌𝗂𝖻𝗅𝖾.. ; 🪽 🥹 𝓗𝖺йти вп от 𝐎𝅄 🥹⎯ׅ ⲙִн𑄜ׄׄжество других кн .. 𝅥 𝅥 предлoжить вп 🎀 🤩🎀 - 🤩𝓮 𝓪𝓻𝓮 𝓽𝓱𝓮 𝓬𝓸𝓸𝓵𝓮𝓼𝓽 VP CF!!! 🎀 🎀 🎀🎀 ܳ ݂ㅤؚۡ꒰ঌ۪ׄ платим зппп админам? ..бракь
Signed ◟ 𝗸ɑ꯭𝐞𝐫ꭎ 𖥻𝗐𝖾𝗅𝗌𝗅𝗏𝗋𝗇𝗈𝟏
ㅤ꒰🤩🤩꒱ 𝓃𝐞𝐰 𝐩𑄝𝘀𝗍 ︵ ❤️ ◟ ⎯ׅ⎯ׄ𝔀𝔀 ִ 𝐤𝐚𝐢𝐬𝐚𝐞𝐝𝐚𝐢𝐥𝐲 ┊❤️ ֗ 𓏏𓏏 #kaisae 🤩 #kise 𓈒 #art ︶⏝ 𝓬𝐫ᧉ𝖽𝐢𝗍、ხ𝑜𝐭🗒 𝗯ᦅᦅ𝐬𝐭 ꛁ𐑼
custom 52401249159185947941custom 53890543586063532811custom 54159048620533667251custom 54451860378170538241
Signed лимит на ссылки ◟ 𝗸ɑ꯭𝐞𝐫ꭎ 𖥻𝗐𝖾𝗅𝗌𝗅𝗏𝗋𝗇𝗈𝟏
ㅤ꒰🤩🤩꒱ 𝓃𝐞𝐰 𝐩𑄝𝘀𝗍 ︵ ❤️ ◟ ⎯ׅ⎯ׄ𝔀𝔀 ִ 𝐤𝐚𝐢𝐬𝐚𝐞𝐝𝐚𝐢𝐥𝐲 ┊❤️ ֗ 𓏏𓏏 #kaisae 🤩 #kise 𓈒 #edit #take ︶⏝ 𝓬𝐫ᧉ𝖽𝐢𝗍、ხ𝑜𝐭🗒 𝗯ᦅᦅ𝐬𝐭 ꛁ𐑼
custom 52401249159185947941custom 53890543586063532811custom 54159048620533667251custom 54451860378170538241
Signed лимит на ссылки ◟ 𝗸ɑ꯭𝐞𝐫ꭎ 𖥻𝗐𝖾𝗅𝗌𝗅𝗏𝗋𝗇𝗈𝟏
🤩🤩🤩🤩𝐦𝐢𝐳𝐢 𝑑𝑎𝑖𝑙𝑦 𝒄𝒇🤩🤩💍 🤩🐏понравилась прелестная 🤩 🤩 💕изи из 𝑎𝑙𝑖𝑒𝑛 𝑠𝑡𝑎𝑔𝑒🥹 𝒄𝒓🤩🤩soujer2🤩🤩kilk4abannerz
Signed лимит на ссылки ◟ 𝗸ɑ꯭𝐞𝐫ꭎ 𖥻𝗐𝖾𝗅𝗌𝗅𝗏𝗋𝗇𝗈𝟏
ㅤ꒰🤩🤩꒱ 𝓃𝐞𝐰 𝐩𑄝𝘀𝗍 ︵ ❤️ ◟ ⎯ׅ⎯ׄ𝔀𝔀 ִ 𝐤𝐚𝐢𝐬𝐚𝐞𝐝𝐚𝐢𝐥𝐲 ┊❤️ ֗ 𓏏𓏏 #kaisae 🤩 #kise 𓈒 #edit #take ︶⏝ 𝓬𝐫ᧉ𝖽𝐢𝗍、ხ𝑜𝐭🗒 𝗯ᦅᦅ𝐬𝐭 ꛁ𐑼
custom 54451860378170538248custom 54159048620533667254custom 52401249159185947943custom 53890543586063532813custom 52513992480202679721custom 54450785691453709561custom 54452672985982938501
Signed 𖥻 𝗸ɑ꯭𝐞𝐫ꭎ #welskotakstanno1
ㅤ ㅤ ㅤ🌟ㅤ🤩𝒆𝒍𝒄𝒐𝒎𝒆 𝒕𝒐 . . . ㅤ ㅤ 𝒁𝑶𝑴𝑩𝑰𝑬 𝑺𝑻𝑨𝑮𝑬 ㅤ ㅤ 𝑫𝑨𝑰𝑳𝒀 ❗️ㅤ🌟 ㅤ ㅤ ㅤ ㅤ ㅤㅤ ㅤ ㅤㅤㅤ 🤩 🤩скали стикеры или гифки по зомст ?? 🌟 🤩🤩ли же хотели найти больше контента не только по зомст, но и по алнст ??? 🌟 🤩огда . . . Мы рады тебя видеть в @dailyzomst 🧁 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤩 🤩десь мы также выкладываем аватарки и нарезки по алнст и зомстㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ🪦 ㅤ ㅤㅤ ㅤㅤ ㅤ⭐️⭐️⭐️⭐️ 🤩ni : база 🤩 хейтеры алнст
Signed ㅤㅤ५ ִ۫ ﹫𝒲︣𝖾𝗅𝗌 ೀ ׄ ۪ 𝆹𝅥 #𝗄𝖺𝖾𝗋𝗎𝗍𝗋𝗎𝖾𝖿𝖺𝗇
🎀 ᴡᴇʟᴄᴏᴍᴇ 💜💜💜 🎀 🌟 🥹 🥹 🤩 ищете разговорный флуд по Блю Локу с необязательной ролевой, небольшой нормой и приятными участниками? 🤩💘 тогда добро пожаловать к нам! 🪦🤩🤩🤩🤩🪦 Здесь в этом флуде есть: • конкурсы • привелегии для участников и админов. • норма — 110 сообщений. • администрация с которой можно поговорить просто так или узн…
Signed 𝓁subasa #нитакусиккиссер
ㅤ 🌸🥹𝗿𝗻𝗶𝘀 𝐝𝐚𝐢𝐥𝐲𝐜𝐟 ︶⏝ ◜ понравилась химия между ֗֗ ⏜ двумя парнями из 𝐛𝐥𝐥𝐤 🖤 🤩 и вы хотите видеть ⸝⸝ ︶ 🤩больше контента с ними ❓ ִ 🤩🤩 ֺ ꒱ ꒱ 𝒕𝒉𝒆𝒏. . . ⏜
Signed 𖥻 𝗸ɑ꯭𝐞𝐫ꭎ #welskotakstanno1
да почему вы выходите 🥲 я думала что к др 200 пдп набью ...
Signed 𖥻 𝗸ɑ꯭𝐞𝐫ꭎ #welskotakstanno1
ㅤ꒰🤩🤩꒱ 𝓃𝐞𝐰 𝐩𑄝𝘀𝗍 ︵ ❤️ ◟ ⎯ׅ⎯ׄ𝔀𝔀 ִ 𝐤𝐚𝐢𝐬𝐚𝐞𝐝𝐚𝐢𝐥𝐲 ┊❤️ ֗ 𓏏𓏏 #kaisae 🤩 #kise 𓈒 # ︶⏝ 𝓬𝐫ᧉ𝖽𝐢𝗍、ხ𝑜𝐭🗒 𝗯ᦅᦅ𝐬𝐭 ꛁ𐑼
custom 54451860378170538247custom 54159048620533667256custom 53890543586063532814custom 54450785691453709562custom 52401249159185947941custom 54452672985982938501
Signed ㅤ ◟ 𝗄𝖺𝖾𝗋𝗎 𓈒 ♡֗֔
🥹❔ Itoshi Sae's Official Channel Менеджер сказал, что мне нужно больше взаимодействовать с фанатами. Что ж. Я нашел время в своем графике и для вас. И хоть это странно: носить на своих плечах людей, которые совсем не смыслят в футболе, но так уж быть, я потерплю. ⏬Go into Itoshi's only channel.⏬ https://t.me/Itohi_Sae
custom 53890543586063532812
Signed 𝓁subasa #нитакусиккиссер
у нас кстати немного изменится расписание , иначе снова постов не будет арты выходят , но их мало , так как всё же это рейрпейринг ... тейки залью завтра
custom 544518603781705382410custom 53890543586063532815custom 54159048620533667254custom 52401249159185947942custom 54452672985982938502
Signed ㅤ ◟ 𝗄𝖺𝖾𝗋𝗎 𓈒 ♡֗֔
Showing the 12 most recent of 19 posts we hold for @kaisaedaily. 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 — 171,866 of 1,481,217entries 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.
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 22 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“ㅤ۪ 𝐤𝐚𝐢𝐬𝐚𝐞 ♡ִ֔ 𝓭𝒂𝒊𝒍𝒚𝒄𝓯 ֺ” (@kaisaedaily), 202 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/kaisaedaily.
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.