Channel
@lyaashoppie
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
738subscribers
+11 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002258963916 |
|---|---|
| Type | Channel |
| Username | @lyaashoppie |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/lyaashoppie |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 00:59 | 738 | +3 |
| 4 Sept 2026, 01:36 | 735 | +1 |
| 27 Aug 2026, 03:49 | 734 | +7 |
| 21 Aug 2026, 01:37 | 727 | no change |
| 20 Aug 2026, 04:45 | 727 | first reading |
19 posts held, back to 14 August 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 19 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
64 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5857429205184157367 | 24 | 37.5% | |
| custom 5859503068797735816 | 17 | 26.6% | |
| 🤣 | 12 | 18.8% | |
| 😭 | 7 | 10.9% | |
| 🍓 | 4 | 6.25% |
Custom emoji. 2 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 18 of the 19 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 14 August 2026 to 19 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.
💎💎 Event Skin Giftလေးလည်းရမယ်နော် 🗡🗡🪄🏹ကြိုက်တဲ့တကောင်ယူ Price - 170,000ks (End Event Gift) End Eventဆိုပေမယ့် Order confirmedဖြစ်ရင် Friend 8 days giftလေးရှာပေးပါတယ် မရရင်တော့ End Eventလေးယူပေးပါ ❤️ Contact me ✉️@hlyniieOwO
custom 58574292051841573672
Signed Lya
Island Giftနောက်တခုထပ်ရမယ်နော်💕 Price - 16,000ks ✉️@hlyniieOwO Dia499 or 999 Pf gift, Starlight Cardရောင်းချင်ရင် contact me ❤️
custom 58574292051841573671
Signed Lya
ASPIRANT 5.0 ဘယ်နေ့လာမလဲတော့မသိသေးဘူးနော် 🌧
custom 58574292051841573672
Signed Lya
Island Giftတခုရ Price - soldout ❤️@hlyniieOwO
custom 58574292051841573673
Signed Lya
Starlight Card lyy lr sell kya pr owm shink
Signed Lya
🀄️🀄️ Exorcist Skin Gift ⚔Yuzhong, 🗡Hayabusa 🏹 Granger End Event Gift - 180,000ks (Event နောက်ဆုံးရက် Giftပါမယ်) 🪄Kagura End Event Gift - 190,000ks (Event နောက်ဆုံးရက် Giftပါမယ်) ✔️Full Prepaid ✔️Cancelမရပါ။ Skin 2ကောင်နဲ့အထက်ဝယ်ရင် ဈေးလျှော့ပေးပါမယ်နော်ရှင့် 🩷 ❤️🔥 @hlyniieOwO
custom 58595030687977358163🍓1
Signed Lya
အရမ်းတန်တယ် နောက် ထပ်မရောင်းနဲ့
🤣12😭1
Signed Lya
Mochi Chat Bean Idပဲပေးရပါမယ် 500 Beans - 7,900ks 2800 Beans - 33,000ks 4000 Beans - 45,000ks 6000 Beans - 62,000ks ✉️@hlyniieOwO
custom 58574292051841573671
Signed Lya
ဂျယ်ဂျယ်လာ coll revamp 😍
custom 58574292051841573674
Signed Lya (sleep pr p)
Discount Diaလေးက ရတော့ဘူးနော် သူတို့ဖက်ကဈေးအရမ်းတက်သွားလို့ပါ 🥺
😭6
Signed Lya
Weeklypass - 6,400ks Weekly Elite Bundle - 3,400ks Monthly Elite Bundle - 17,000ks 🤍မျှားလေးကိုဖိကြည့်ပေးပါရှင့် 💎86 - 5,200ks 💎112 - 7,000ks 💎172 - 10,200ks 💎257 - 14,900ks 💎343 - 20,100ks 💎429 - 25,100ks 💎514 - 29,800ks 💎600 - 34,900ks 💎706 - 40,200ks 💎878 - 50,500ks 💎963 - 55,100ks 💎1049 - 60,300ks 💎1135 - 65,300ks 💎1412 - 80,500ks 💎1755 - 100,500ks 💎2195 - 121,800ks 💎2901 -162,100ks 💎3688 - 203,300ks 💎5100 - 2…
custom 58595030687977358163
Signed Lya
နောက်လတွက် Collector Skinတွေပါ Yss Coll ပြန်ပါမယ်နော်💘
custom 58595030687977358168custom 58574292051841573671
Signed Lya
Showing the 12 most recent of 19 posts we hold for @lyaashoppie. 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 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Lyaa’s Shoppie” (@lyaashoppie), 738 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/lyaashoppie.
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.