Channel
@lunika_milk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
217subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002462220868 |
|---|---|
| Type | Channel |
| Username | @lunika_milk |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 17 August 2026 |
| On Telegram | t.me/lunika_milk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 14:16 | 217 | no change |
| 8 Aug 2026, 17:15 | 217 | first reading |
4 posts held, back to 19 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 8 August 2026 |
|---|---|
| Posts held | 4 (19 July 2026 – 8 August 2026) |
| Views total | 437 |
| Reactions total | 179 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 17: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.
Measured directly from 1 video 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.
179 reactions across 4 posts, in 15 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5107121671525893351 | 42 | 23.5% | |
| custom 5382052118804841541 | 23 | 12.8% | |
| custom 5307640736659817996 | 17 | 9.50% | |
| custom 5408896343009689442 | 16 | 8.94% | |
| custom 5258253474658814356 | 13 | 7.26% | |
| custom 5381851118630354721 | 13 | 7.26% | |
| custom 5316871398767992676 | 9 | 5.03% | |
| custom 5305792161260794482 | 8 | 4.47% | |
| custom 5307787405498021988 | 7 | 3.91% | |
| custom 5307818930557975574 | 7 | 3.91% | |
| custom 5257985077857520212 | 6 | 3.35% | |
| custom 5382008048145415843 | 6 | 3.35% | |
| custom 5233560303219776999 | 4 | 2.23% | |
| custom 5276227582080065858 | 4 | 2.23% | |
| custom 5308010700847743146 | 4 | 2.23% |
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 4 of the 4 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 179reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 19 July 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 53168713987679926769custom 52335603032197769994custom 52762275820800658584
Прекрасные фото прекрасных фей с Эпик Кона!✨ ✨✨✨✨✨✨✨✨ 🧚♀️ Муза 🧚♀️Стелла 🧚♀️Блум 🧚♀️Флора 🧚♀️Лейла 🧚♀️Текна ✨✨✨✨✨✨✨✨ #epicconrussia #epiccon
custom 530764073665981799617custom 53057921612607944828custom 53077874054980219887custom 53080107008477431464
😷Потусили с девочками на Винкс вечеринке!🤩🌟 🤩🤩 🤩🤩 вайб 🤩🤩 🤩🤩 присутствует✨ 💫💫💫💫💫💫💫💫
custom 540889634300968944216custom 525825347465881435613custom 53078189305579755747custom 52579850778575202126
17.07.2026 💍🤍 До сих пор не верится, что этот день уже позади. Наша свадьба получилась именно такой, о какой мы мечтали: невероятно трогательной, тёплой и такой счастливой. Столько улыбок, объятий, добрых слов и моментов, которые хочется сохранить в памяти навсегда. Спасибо каждому, кто был рядом и разделил с нами этот день. Было сказано столько искренних и тёплых слов, что я прослезилась раз пять. 😭 Спасибо за каж…
custom 510712167152589335142custom 538205211880484154123custom 538185111863035472113custom 53820080481454158436
Showing the 4 most recent of 4 posts we hold for @lunika_milk. 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 — 413,610 of 1,480,975entries 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Lunika” (@lunika_milk), 217 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/lunika_milk.
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.