Channel
@uz_moshinabozor77
On this record: Topic · Growth · Engagement · Posts · Cite this entry
644subscribers
-30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001429816918 |
|---|---|
| Type | Channel |
| Username | @uz_moshinabozor77 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/uz_moshinabozor77 |
Automotive — 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 97% 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 |
|---|---|---|
| 25 Sept 2026, 16:39 | 644 | -9 |
| 14 Sept 2026, 02:01 | 653 | -2 |
| 6 Sept 2026, 16:59 | 655 | -4 |
| 30 Aug 2026, 01:18 | 659 | -4 |
| 23 Aug 2026, 14:49 | 663 | -2 |
| 15 Aug 2026, 05:03 | 665 | -9 |
| 7 Aug 2026, 20:58 | 674 | no change |
| 7 Aug 2026, 09:48 | 674 | first reading |
3 posts held, back to 3 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 3 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
#Jetour T2 model ➖Йили : 2024-25 salondan xaydalgan ➖Пробег : 25.000 km ➖Екилги тури : benzin ➖Узатма : aftomat ➖Нархи : 29.000$ kelishiladi ➖Кушимча малумот : comfort 1.5 turbo, 450 millionligi 5 xil funksiyasi bor sport, eco, normal. Full 📞 Мурожат Учун : 998104711 @uz_moshinabozor77
Signed Uz_moshinabozor
#Zeekr 9xHyper(Obsidion) ➖Йили :2026 ➖Пробег : 0km ➖Екилги тури : гибрид ➖Узатма : автомат ➖Нархи : 141.000 ➖Кушимча малумот :сидения айланaди(full) 📞 Мурожат Учун : +998999130709 @uz_moshinabozor77
Signed Uz_moshinabozor
#Malibu 2 primer ➖Йили : 2021 ➖Пробег : 125.000 km ➖Екилги тури : propan ➖Узатма : aftomat ➖Нархи : 19.500$ ➖Кушимча малумот : kraska oldi krilo sopir tomon, 5.000-6000.$ bosa varyantga gaplashilnadi 📞 Мурожат Учун : 507572602 @uz_moshinabozor77
Signed Uz_moshinabozor
Showing the 3 most recent of 3 posts we hold for @uz_moshinabozor77. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Uz_moshinabozor” (@uz_moshinabozor77), 644 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/uz_moshinabozor77.
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.