❗️NALICHIDA 💸41000 ✔️Bejovy 1 #5653🚫

Channel
💎Zuhra 💎 наличии
@zuhrushanalichii
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,305subscribers
-17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001542240300 |
|---|---|
| Type | Channel |
| Username | @zuhrushanalichii |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/zuhrushanalichii |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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 |
|---|---|---|
| 15 Sept 2026, 07:57 | 1,305 | -2 |
| 11 Sept 2026, 06:17 | 1,307 | -5 |
| 6 Sept 2026, 11:41 | 1,312 | +6 |
| 2 Sept 2026, 04:34 | 1,306 | +2 |
| 30 Aug 2026, 13:35 | 1,304 | -2 |
| 27 Aug 2026, 14:33 | 1,306 | +1 |
| 24 Aug 2026, 11:58 | 1,305 | -4 |
| 20 Aug 2026, 18:37 | 1,309 | -7 |
| 17 Aug 2026, 14:58 | 1,316 | -2 |
| 14 Aug 2026, 06:35 | 1,318 | -3 |
| 10 Aug 2026, 23:22 | 1,321 | -1 |
| 7 Aug 2026, 07:01 | 1,322 | no change |
| 7 Aug 2026, 06:57 | 1,322 | first reading |
Engagement
14 posts held, back to 27 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 14 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
❗️NALICHIDA 🇹🇷Turkiya 💸 278000 ✅ rozovy M
❗️NALICHIDA 🇹🇷Turkiya 💸 204000 6-7 7-8 #3752🚫
❗️NALICHIDA ❤️ USA 💸 413000 🚫 🤩 365000 1 Original❤️
❗️NALICHIDA 🇹🇷 Turkiya 💸364000 🚫 🤩 300000 36 razmer 38 gayam bemaaalol keladi qizlaaa
❗️NALICHIDA 💸129000 1 #1366🚫
❗️NALICHIDA 🇹🇷Turkiya 🚫829000 💸 799000 36 ❗️750.000
Video message, posted without a caption
Photo, posted without a caption
❗️NALICHIDA 🇹🇷Turkiya 💸 231000 44 #4405🚫 ❗️199.000
❗️NALICHIDA 🇹🇷Turkiya 💸 241000 2xl #4405🚫 ❗️199.000
❗️NALICHIDA 🇹🇷Turkiya 💸 201000 2xl #4405🚫 ❗️195.000
Showing the 12 most recent of 14 posts we hold for @zuhrushanalichii. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“💎Zuhra 💎 наличии” (@zuhrushanalichii), 1,305 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zuhrushanalichii.
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.