🤍
custom 53976919931051388358custom 51906494438792535187custom 51927891579314155997

Channel
@premiumbymee
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
125subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002358556204 |
|---|---|
| Type | Channel |
| Username | @premiumbymee |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/premiumbymee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 03:16 | 125 | +4 |
| 29 Aug 2026, 20:44 | 121 | +1 |
| 15 Aug 2026, 00:24 | 120 | -1 |
| 9 Aug 2026, 03:45 | 121 | no change |
| 7 Aug 2026, 19:30 | 121 | first reading |
7 posts held, back to 8 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 page of 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 7 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
95 reactions across 7 posts, in 15 distinct kinds. The most used accounts for 18.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5397691993105138835 | 18 | 18.9% | |
| custom 5192789157931415599 | 16 | 16.8% | |
| custom 5190649443879253518 | 12 | 12.6% | |
| custom 5294442675821397842 | 7 | 7.37% | |
| custom 5190868379837170372 | 6 | 6.32% | |
| custom 5192765144769263995 | 6 | 6.32% | |
| custom 5269328125140956116 | 6 | 6.32% | |
| custom 5296747286552942173 | 5 | 5.26% | |
| custom 5300869299810882448 | 4 | 4.21% | |
| custom 5431559390782064045 | 4 | 4.21% | |
| custom 5262480061780476581 | 3 | 3.16% | |
| custom 5278576194751586100 | 3 | 3.16% | |
| custom 5190592617166963185 | 2 | 2.11% | |
| custom 5192825772527612237 | 2 | 2.11% | |
| custom 5449587932618841358 | 1 | 1.05% |
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 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 7 of the 7 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 95 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 8 July 2026 to 5 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 53976919931051388358custom 51906494438792535187custom 51927891579314155997
Video, posted without a caption
custom 51927891579314155997custom 53976919931051388357custom 51906494438792535185
Римская империя 💋
custom 52944426758213978426custom 52967472865529421735custom 53976919931051388353custom 51927891579314155992
😀
custom 52624800617804765813custom 54315593907820640453custom 52944426758213978421custom 54495879326188413581
🫦
custom 52693281251409561165custom 51927651447692639954custom 51908683798371703723custom 54315593907820640451
🤩
custom 51908683798371703723custom 52785761947515861003custom 51928257725276122372
🫦🫦
custom 53008692998108824484custom 51905926171669631852custom 51927651447692639952custom 52693281251409561161
Showing the 7 most recent of 7 posts we hold for @premiumbymee. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Nika Rogaleva” (@premiumbymee), 125 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/premiumbymee.
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.