Channel
@daily_kafka
On this record: Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Cite this entry
273subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1001908829747 |
|---|---|
| Type | Channel |
| Username | @daily_kafka |
| Created | 28 April 2023 โ measured โ cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/daily_kafka |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:07 | 273 | -1 |
| 8 Aug 2026, 08:46 | 274 | no change |
| 7 Aug 2026, 19:49 | 274 | first reading |
19 posts held, back to 12 May 2025 โ 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ we hold 19 posts for this entry, the most recent from 2 May 2026. An engagement rate over an empty window would be a number about nothing.
327 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 24.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ | 79 | 24.2% | |
| customย 5193105954719156517 | 69 | 21.1% | |
| โค | 59 | 18.0% | |
| ๐ฅฐ | 52 | 15.9% | |
| ๐ | 37 | 11.3% | |
| โคโ๐ฅ | 26 | 7.95% | |
| ๐ฅ | 3 | 0.917% | |
| โก | 1 | 0.306% | |
| ๐ | 1 | 0.306% |
Custom emoji. One 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 count beside it isTelegramโ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 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 327reactions 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 12 May 2025 to 2 May 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.
ัะฐัะฟะธัะฐะฝะธะต ะฟะพััะพะฒ โ ( ะดะฒะฐ ะฟะพััะฐ ะฒ ะดะตะฝั ) 10:00 20:00 ะพัะพัะผะปะตะฝะธะต (ะฝะต ะทะฐะฑัะฒะฐะนัะต ะฒัะดะตะปััั ะถะธัะฝัะผ ััะธััะพะผ ั ะตััะตะณะธ, ััะพ ัะปะตะผะตะฝั ะพัะพัะผะปะตะฝะธั) ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ โฆ via โฆ ๐ซ๐ ๏นซkafka.daily๐ โ
โค6๐2๐2โก1๐1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ Distrbeachboy via X ๐ซ๐ ๏นซkafka.daily๐ โ
customย 519310595471915651720๐7โค4๐1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ i_imperiat via X ๐ซ๐ ๏นซkafka.daily๐ โ
customย 519310595471915651713โค7๐2โคโ๐ฅ1๐1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ Distrbeachboy via X ๐ซ๐ ๏นซkafka.daily๐ โ
โคโ๐ฅ9customย 51931059547191565177๐6โค2๐2
tw: NSFWยฟ ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ shafroii via X ๐ซ๐ ๏นซkafka.daily๐ โ
customย 519310595471915651712๐ฅฐ7๐4โคโ๐ฅ2๐2โค1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ xigpicisklev630 via X ๐ซ๐ ๏นซkafka.daily๐ โ
๐5customย 51931059547191565175โค3๐3๐ฅฐ1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ xigpicisklev630 via X ๐ซ๐ ๏นซkafka.daily๐ โ
๐9โค2โคโ๐ฅ2customย 51931059547191565172๐1
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ Kystery via pixiv ๐ซ๐ ๏นซkafka.daily๐ โ
๐ฅฐ8โค3๐2โคโ๐ฅ1๐1๐ฅ1customย 51931059547191565171
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ YUREITH via pixiv ๐ซ๐ ๏นซkafka.daily๐ โ
โค5๐ฅฐ5๐3โคโ๐ฅ2๐2customย 51931059547191565171
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ nutnutbunny via pixiv ๐ซ๐ ๏นซkafka.daily๐ โ
๐5โค1โคโ๐ฅ1๐1๐ฅฐ1customย 51931059547191565171
ใ คใ ค โ โจ . #fa ๏ฝ #only ๐คฉ ๐ซ๐ฆ cr โณ Oz via pixiv ๐ซ๐ ๏นซkafka.daily๐ โ
๐10โค2โคโ๐ฅ2๐2๐ฅฐ1customย 51931059547191565171
โ ๐๐ฆ๐๐๐๐ข๐ช๐ ๐๐๐๐๐ข๐ข๐๐๐.๐ง.๐ ๐ ?? โค๏ธ ๐ด ะธัะบะฐะปะธ ะฐะบัะธะฒะฝัะน ะดะตะนะปะธ & ะบั ะฟะพ ัะฐะบะพะน ะฟะตัะตะฝัะบะต ะบะฐะบ ััะดะพั ะผะธะปะบ ?๐คฉ โฆ ะบะปะธะบะฝะธ, ััะพะฑั ะทะฐะนัะธ โ ๐
๐1
Showing the 12 most recent of 19 posts we hold for @daily_kafka. 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 โ 776,175 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.
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.
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 14 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐ฝ๐บ๐๐ ๐ ๐๐บ๐ฟ๐๐บ ` ๐๐๐โ (@daily_kafka), 273 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/daily_kafka.
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.