#. daily & cf millsage ﹒ ♪ 🪽 cr : @warinsann on twt(X) ⤸ ; tags ⇣⇡ #fa , #nagi , #natsume
custom 54180263353794262513custom 54180519076147103042🔥1

Channel
@dailymillsage
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
112subscribers
+0 since we began measuring on 6 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004320754568 |
|---|---|
| Type | Channel |
| Username | @dailymillsage |
| Description | бот для тейков @millsagetakesbot |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dailymillsage |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 08:22 | 112 | no change |
| 6 Oct 2026, 07:47 | 112 | first reading |
20 posts held, back to 3 October 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.
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 October 2026 |
|---|---|
| Posts held | 20 (3 October 2026 – 6 October 2026) |
| Views total | 1,105 |
| Reactions total | 202 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 08:22 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 6 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
202 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 21.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5406733973005053022 | 44 | 21.8% | |
| custom 5416121603283001162 | 32 | 15.8% | |
| custom 5416070677855768348 | 24 | 11.9% | |
| custom 5418026335379426251 | 19 | 9.41% | |
| custom 5418051907614710304 | 16 | 7.92% | |
| 💘 | 15 | 7.43% | |
| custom 5416035759771653670 | 13 | 6.44% | |
| 🔥 | 13 | 6.44% | |
| ❤ | 12 | 5.94% | |
| custom 5417843498621633657 | 9 | 4.46% | |
| custom 5474256163182779500 | 5 | 2.48% |
Custom emoji. 8 of the rows above are 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 20 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 202 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 3 October 2026 to 6 October 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.
#. daily & cf millsage ﹒ ♪ 🪽 cr : @warinsann on twt(X) ⤸ ; tags ⇣⇡ #fa , #nagi , #natsume
custom 54180263353794262513custom 54180519076147103042🔥1
#. daily & cf millsage ﹒ ♪ 🪽 cr : @lruka__1019 on twt(X) ⤸ ; tags ⇣⇡ #fa , #hotaru , #mahoro
custom 54067339730050530223custom 54178434986216336573custom 54161216032830011622
#. daily & cf millsage ﹒ ♪ 🪽 cr : @odilodet on twt(X) ⤸ ; tags ⇣⇡ #fa , #all
🔥4custom 54180519076147103043❤2
t.me/ほたほう ︩︪ׄ ˖ ִִ۫𝆬 —— ྀི Любишь взаимодействия между ᜊШиᦅми и Изуми?ഒ . • Хочешь видеть коྀིнтент по ним? . . 𐙚DAILY HOTAHOU
custom 54160706778557683483
#. daily & cf millsage ﹒ ♪ 🪽 Здравствуйте я канаточку поскетчила! Канал- @kryandahoi #take @millsagetakesbot
custom 54067339730050530229❤4custom 54160357597716536703custom 54742561631827795002custom 54160706778557683481custom 54178434986216336571
#. daily & cf millsage ﹒ ♪ 🪽 всем привет !! я сделала аним пак с хокой , может , кто искал. https://t.me/addstickers/izumihouka_by_TgEmodziBot #take @millsagetakesbot
custom 54160706778557683486custom 54067339730050530221custom 54160357597716536701
#. daily & cf millsage ﹒ ♪ 🪽 cr : @U__spring on twt(X) ⤸ ; tags ⇣⇡ #fa , #hotaru
custom 54161216032830011625❤3custom 54742561631827795003💘1custom 54067339730050530221
#. daily & cf millsage ﹒ ♪ 🪽 cr : @veitalya on tiktok ⤸ ; tags ⇣⇡ #video , #all
custom 54067339730050530225❤3custom 54178434986216336572💘1🔥1
#other : 🤩🤩🤩🤩🤩 :: — Реплики после лайвов 💙 » читать! 🤩 Переведено @ournotesbd 💙#hotaru #natsume #nagi 💙#mahoro #hoka / #millsage
💘2
#other : 🤩🤩🤩🤩🤩 :: — Профили персонажей 🔳🔳 и базовые реплики! 🎵🎵 — Шиоми Хотару 🎵🎵 — Изава Нацуме 🎵🎵 — Котохира Наги 🎵🎵 — Хамасаки Махоро 🎵🎵 — Изуми Хока Переведено @ournotesbd 💙#hotaru #natsume #nagi 💙#mahoro #hoka / #millsage
💘2
#. daily & cf millsage ﹒ ♪ 🪽 привет я нармсовала хоуку 😍😍😍 @pvg_v9 #take @millsagetakesbot
custom 54160706778557683488💘5custom 54180263353794262515custom 54067339730050530223custom 54160357597716536702
#. daily & cf millsage ﹒ ♪ 🪽 cr : @toweler170 on twt(X) ⤸ ; tags ⇣⇡ #fa , #natsume , #houka
custom 54067339730050530224custom 54180519076147103044custom 54160706778557683483💘1
Showing the 12 most recent of 20 posts we hold for @dailymillsage. 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 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“daily & cf millsage” (@dailymillsage), 112 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/dailymillsage.
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.