Lilshah store pinned a voice message

Channel
Lilshah store
@lilshahstore
On this record: Topic · Growth · Engagement · Posts · Cite this entry
16,741subscribers
+268 since we began measuring on 16 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002465510055 |
|---|---|
| Type | Channel |
| Username | @lilshahstore |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/lilshahstore |
Topic
Ecommerce storefront — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 20:57 | 16,741 | +92 |
| 4 Oct 2026, 11:15 | 16,649 | +135 |
| 25 Sept 2026, 20:15 | 16,514 | -17 |
| 19 Sept 2026, 04:57 | 16,531 | +58 |
| 16 Sept 2026, 23:22 | 16,473 | first reading |
Engagement
17 posts held, back to 15 September 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.
- ERR · 30 days
- 12.0%
- avg views ÷ 16,741 subscribers
- Avg views / post
- 2,010
- 16 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 17
- of 17 held
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 16 September 2026 |
|---|---|
| Posts held | 17 (15 September 2026 – 16 September 2026) |
| Views total | 32,230 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Sept 2026, 23:22 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.
Recent posts
من خیلی منتظر بودم عطر بن بن برسه بهتون و نظرتونو بدونم چون خیلی مورد علاقه خودمه و واسه شروع پاییز یکی برا خودم برداشتم 🤗⭐️❤️
Voice message, posted without a caption
Sticker, posted without a caption
سلام شهرزاد قشنگم بستم الان رسید 🥳 واقعااااا عالی بود همون چیزی که میخواستم بود عاشقشمممم❤️🥺 مرسی که اینقدر خوبی💋🥹
سلام دافییی من بستم همین امروز یعنی دو روز بعد از سفارشم رسیدددد و عاشقشون شدم کلی بوس بهت😭✨🩵💙
صورتی تمام ❤️🩹
حجم پیاما زیاده نقطه پیامتونو میبره بالا تر صبوری کنید همرو جواب میدیم 💋
103 تمام ❤️🩹 104 تمام ❤️🩹
لیپ گلاس هودی موجی سه کد 3/4/5 قیمت اصلی 390 قیمت تخفیفی 320
پلامپر خیس سه کد رنگی 1/2/4 قیمت اصلی : 430 قیمت تخفیف : 380
هر ۴ کد رژگونه موجوده ، یک بار فقط برای تست روی دست استفاده شده ، فقط یک بار . قیمت اصلی : 360 قیمت تخفیفی تست : 280
Showing the 12 most recent of 17 posts we hold for @lilshahstore. 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.
Cite this entry
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Lilshah store” (@lilshahstore), 16,741 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/lilshahstore.
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.