🍭Конфетка 🍭🥰
custom 53483735622499800478custom 59966636912090850317custom 54046519145938367214custom 54676588958476081853custom 52355891641660323241

Channel
@msLimeYana
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
74subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003415820063 |
|---|---|
| Type | Channel |
| Username | @msLimeYana |
| Description | Начинаю канал о своей Большой любви к изделиям из бусин. Занимаюсь плетением уже 3 года и вот решилась на свой канал, что бы все увидели эту красоту🫶 Связь со мной @msLimeY Доставка по всей России - Озон(доставка в стоимость изделия не входит) |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/msLimeYana |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 22:01 | 74 | no change |
| 7 Aug 2026, 18:56 | 74 | first reading |
9 posts held, back to 9 April 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 9 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 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 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.
200 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 37.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348373562249980047 | 74 | 37.0% | |
| custom 5377547320881586194 | 26 | 13.0% | |
| custom 5996663691209085031 | 23 | 11.5% | |
| custom 5235589164166032324 | 22 | 11.0% | |
| custom 5334812855847901773 | 19 | 9.50% | |
| custom 5404651914593836721 | 14 | 7.00% | |
| custom 5438571934210082705 | 12 | 6.00% | |
| custom 5249484362621141855 | 7 | 3.50% | |
| custom 5467658895847608185 | 3 | 1.50% |
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 9 of the 9 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 200 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 9 April 2026 to 30 June 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 53483735622499800478custom 59966636912090850317custom 54046519145938367214custom 54676588958476081853custom 52355891641660323241
Белый хрусталь 🐯
custom 534837356224998004710custom 53775473208815861944custom 52355891641660323243custom 53348128558479017733custom 52494843626211418551
Я от сочетания в восторге ...🥰
custom 53775473208815861946custom 54385719342100827056custom 52355891641660323243custom 53483735622499800472custom 54046519145938367212
Шкатулочка с вставками под украшения 💍
custom 59966636912090850317custom 54046519145938367215custom 53348128558479017734custom 52355891641660323243custom 52494843626211418551
🌼💜
custom 53483735622499800479custom 53775473208815861948custom 53348128558479017733custom 54046519145938367213custom 52355891641660323242
Что то на супер нежном 🥹
custom 534837356224998004710custom 53775473208815861944custom 52494843626211418552custom 52355891641660323241custom 53348128558479017731
Гранатовая шкатулочка ❤️
custom 534837356224998004715custom 52355891641660323243custom 53348128558479017732custom 59966636912090850312custom 53775473208815861941
🌸Шкатулочка напомнила мне: первые цветы после зимы 🌼☀️
custom 534837356224998004711custom 52355891641660323244custom 54385719342100827054custom 52494843626211418553custom 53775473208815861942custom 53348128558479017731
Спец-заказ ❤️ В меру строго и элегантно 💖
custom 53483735622499800479custom 59966636912090850317custom 53348128558479017735custom 52355891641660323242custom 54385719342100827052custom 53775473208815861941
Showing the 9 most recent of 9 posts we hold for @msLimeYana. 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.
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.
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.
“Изделия из бусин msLimeY🍋🟩” (@msLimeYana), 74 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/msLimeYana.
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.