109/200
custom 54543320847745325563custom 54540460743123548441custom 54541825640780576211

Channel
@bbymilssk
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
1,656subscribers
+30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001780997199 |
|---|---|
| Type | Channel |
| Username | @bbymilssk |
| 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 | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/bbymilssk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:14 | 1,656 | +19 |
| 10 Aug 2026, 20:11 | 1,637 | +10 |
| 8 Aug 2026, 02:26 | 1,627 | +1 |
| 7 Aug 2026, 21:16 | 1,626 | no change |
| 7 Aug 2026, 18:48 | 1,626 | first reading |
15 posts held, back to 18 May 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 1 August 2026 |
|---|---|
| Posts held | 15 (18 May 2026 – 1 August 2026) |
| Views total | 2,925 |
| Reactions total | 142 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 21:16 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.
1,697 reactions across 13 posts, in 18 distinct kinds. The most used accounts for 10.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5247135900273515783 | 177 | 10.4% | |
| custom 5413512200197272745 | 139 | 8.19% | |
| custom 5411370549114860594 | 135 | 7.96% | |
| custom 5244676047949044633 | 131 | 7.72% | |
| custom 5188366033106277822 | 126 | 7.42% | |
| custom 5247100183325480695 | 123 | 7.25% | |
| custom 5188662317130225114 | 121 | 7.13% | |
| custom 5413774803087685441 | 114 | 6.72% | |
| custom 5474407277312124381 | 107 | 6.31% | |
| custom 5436066215929872322 | 76 | 4.48% | |
| custom 5435890538882562355 | 70 | 4.12% | |
| custom 5438164466367755830 | 66 | 3.89% | |
| custom 5454046074312354844 | 61 | 3.59% | |
| custom 5204319671947400141 | 60 | 3.54% | |
| custom 5204046421833062077 | 57 | 3.36% | |
| custom 5204194654039349075 | 53 | 3.12% | |
| custom 5454332084774532556 | 44 | 2.59% | |
| custom 5454182564078057621 | 37 | 2.18% |
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 15 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 1,697reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 May 2026 to 1 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bbymilssk. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 18 May 2026 to 1 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
109/200
custom 54543320847745325563custom 54540460743123548441custom 54541825640780576211
˗ˏˋ — $tïkérs × ⊹ #зелёный #вайб ˎˊ˗ ⌗🤩» @bbymilssk . .
custom 545404607431235484460custom 545433208477453255641custom 545418256407805762136
Channel name was changed to «премиум стикеры милс.»
грустно уходить, пока выложу эти стикеры.. может не уйду(да у меня биполярка) поэтому газ максимальный актив🌞
custom 518836603310627782261custom 518866231713022511437custom 547440727731212438137
˗ˏˋ — $tïkérs × ⊹ #аляска ˎˊ˗ ⌗📚» @bbymilssk . .
custom 518866231713022511484custom 518836603310627782265custom 547440727731212438164
спасибо большое за звезды!! 😭 даже не увидела
custom 524713590027351578318custom 524710018332548069511custom 54744072773121243816
если есть возможность то не уходите🥹
custom 524713590027351578319custom 524710018332548069513custom 524467604794904463311
не знаю временно или нет, но у меня пропала мотивация да и интерес к этому. может буду выкладывать старые или через раз новые. спасибо всем кто был со мной🥹
custom 524713590027351578343custom 524467604794904463319custom 524710018332548069519
Channel name was changed to «премиум стикеры милс. закрыт»
0/250 реакций если понравились и берете стикеры, пожалуйста пишите "+" в комментариях. вам не сложно, а для меня будет видно вашу активность и то, какие стикеры вам больше нужны. если не сложно поставьте звёздочки на пост🌟 у меня тг баганул, простите
custom 524713590027351578322custom 52471001833254806959custom 52446760479490446338
Signed милс
˗ˏˋ — $tïkérs × ⊹ #чб #вайб #бежевый ˎˊ˗ ⌗🦴» @bbymilssk . .
custom 524467604794904463393custom 524713590027351578375custom 524710018332548069571
Signed милс
я вот ставлю реакции на комментарии, мои подписчицы такие красивые. вы просто куколки!! 🥹
custom 541137054911486059446custom 541351220019727274528custom 541377480308768544126
Signed милс
Showing the 12 most recent of 15 posts we hold for @bbymilssk. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 949,657 of 1,480,688entries 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 3 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“премиум стикеры милс.” (@bbymilssk), 1,656 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/bbymilssk.
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.