Channel
@dailykunikida
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
465subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002155312163 |
|---|---|
| Type | Channel |
| Username | @dailykunikida |
| Description | ежедневные посты с куникидой пнг в глав. посте cr :: @BSD_PNGG |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/dailykunikida |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 04:48 | 465 | no change |
| 8 Aug 2026, 03:22 | 465 | -1 |
| 7 Aug 2026, 19:15 | 466 | first reading |
18 posts held, back to 21 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (21 July 2026 – 6 August 2026) |
| Views total | 3,606 |
| Reactions total | 581 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 04: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.
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.
Measured directly from 3 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.
581 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 35.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5384460470176479972 | 205 | 35.3% | |
| custom 5386614542304308730 | 158 | 27.2% | |
| custom 5386822130958627230 | 97 | 16.7% | |
| custom 5386682681960461411 | 91 | 15.7% | |
| custom 5386321123023549090 | 30 | 5.16% |
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 18 of the 18 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 581reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 21 July 2026 to 6 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.
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #art ➤ 「@kuni_kuun」on ×。♯
custom 538661454230430873014custom 53868221309586272308custom 53866826819604614115custom 53844604701764799724
Signed 6 ЛЕТ!! 𐙚𝆹𝅥𝑁𝑖𝑐𝑜𝑙𝑒 𓏴 𝐾𝑢𝑛𝑖𝑘𝑖𝑑𝑎꒱꒱۫
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #art ➤ 「@hebi_er」on ×。♯
custom 538668268196046141113custom 53866145423043087308custom 53868221309586272305custom 53863211230235490902custom 53844604701764799721
Signed 6 ЛЕТ!! 𐙚𝆹𝅥𝑁𝑖𝑐𝑜𝑙𝑒 𓏴 𝐾𝑢𝑛𝑖𝑘𝑖𝑑𝑎꒱꒱۫
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #art ➤ 「@sakiika_ill」on ×。♯
custom 538446047017647997216custom 53866826819604614117custom 53866145423043087304custom 53868221309586272302
Signed 6 ЛЕТ!! 𐙚𝆹𝅥𝑁𝑖𝑐𝑜𝑙𝑒 𓏴 𝐾𝑢𝑛𝑖𝑘𝑖𝑑𝑎꒱꒱۫
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #art ➤「@FalseDmitryTheFirst」 on tg。♯
custom 538446047017647997217custom 53863211230235490905custom 53866145423043087305custom 53868221309586272305custom 53866826819604614113
Signed Люблю кукурузу [📗👓]
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida ⋮ #art ➤ 「@Najibrotianggur」on Twitter。♯
custom 538661454230430873018custom 538446047017647997213custom 53866826819604614116custom 53868221309586272303custom 53863211230235490902
Signed @ irl5012
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #video ➤「@kandyheqrts_」on tiktok。♯
custom 538682213095862723015custom 53866145423043087306custom 53844604701764799724custom 53866826819604614113
Signed 𐙚𝆹𝅥𝑁𝑖𝑐𝑜𝑙𝑒 𓏴 𝐾𝑢𝑛𝑖𝑘𝑖𝑑𝑎꒱꒱۫
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida ⋮ #art ➤ 「@0bluesheep0」on Twitter。♯
custom 538446047017647997218custom 53863211230235490907custom 53866145423043087305
Signed @ irl5012
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida ⋮ #art ➤ 「@Haewol0704」on Twitter。♯
custom 538661454230430873013custom 53844604701764799727custom 53868221309586272304custom 53866826819604614113
Signed @ irl5012
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #video ➤「@FalseDmitryTheFirst」on tg。♯
custom 538446047017647997220custom 538661454230430873010custom 53868221309586272307custom 53866826819604614113custom 53863211230235490901
Signed Люблю кукурузу [📗👓]
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #chuuya ⋮ #art ➤ 「@ilovejavilloyd」on tg。♯
custom 538668268196046141118custom 53866145423043087308custom 53844604701764799727custom 53868221309586272305custom 53863211230235490903
Signed Люблю кукурузу [📗👓]
» 𝑲𝒖𝒏𝒊𝒌𝒊𝒅𝒂𝑫𝒐𝒑𝒑𝒐 𝒅𝒂𝒊𝒍𝒚・𝒄𝒇 ⎚-⎚ #kunikida #solo ⋮ #art ➤ 「@Osikatu_1129」on ×。♯
custom 538446047017647997211custom 53866145423043087307custom 53863211230235490906custom 53866826819604614113custom 53868221309586272301
Signed 𐙚𝆹𝅥𝑁𝑖𝑐𝑜𝑙𝑒 𓏴 𝐾𝑢𝑛𝑖𝑘𝑖𝑑𝑎꒱꒱۫
Не знаю, надо такое под блюр, но на всякий случай кину. Снова выкидываю Райдэн Эи и Куникида Доппо Неанон: Эвглена ⁞ ✎ #take || ⎚-⎚ 𝅄 ꣑ৎ ࣪ㅤ𓈒 @dailykunikida_bot
custom 538661454230430873014custom 53866826819604614114custom 53844604701764799723
Signed Люблю кукурузу [📗👓]
Showing the 12 most recent of 18 posts we hold for @dailykunikida. 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 — 192,556 of 1,345,403entries 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.
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 2 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.
@dailykunikida named 6 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“daily × cf kunikida doppo [ 📗👓 ]” (@dailykunikida), 465 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dailykunikida.
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.