Channel
@uzbek_ozbek_odam_qoshish
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
116subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001772112089 |
|---|---|
| Type | Channel |
| Username | @uzbek_ozbek_odam_qoshish |
| Created | 16 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/uzbek_ozbek_odam_qoshish |
Marketing & affiliate — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 16 Sept 2026, 13:37 | 116 | -1 |
| 8 Sept 2026, 12:00 | 117 | -3 |
| 30 Aug 2026, 07:04 | 120 | -3 |
| 22 Aug 2026, 11:35 | 123 | -2 |
| 14 Aug 2026, 13:37 | 125 | -2 |
| 9 Aug 2026, 02:01 | 127 | no change |
| 6 Aug 2026, 09:46 | 127 | first reading |
20 posts held, back to 20 September 2023 — 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 20 posts for this entry, the most recent from 17 January 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 13 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.
Assalomu alaykum hurmatli mijoz! Bizga murojaat qilayotganda iltimos qaysi kanal yoki guruhga qancha odam qo'shish kerakligini yozing shunda ishiz tez bitadi. Diqqat kanal va guruhga aktiv odam so'raganlar uchun 100% aktiv odamlar qo'shamiz 1000 tasi 120 ming so'mdan qolgani kelishuv asosida. Faqat odam soni uchun qo'shiladigan chet el odamlarni 1000 tasi 25 ming so'mdan qo'shib beramiz! Undan tashqari Telegram, I…
✏️✏️✏️✏️✏️✏️ Faqat 3kun super aksiya kanallarga 100% uzbek odam aktiv qo'shamiz ular siz va bizga o'xshagan odamlar qo'shiladi ✅ 1000 tasi =100 ming 😍 10.000 tasi = 900 ming 😍 Diqqat aksiyaga ulgurib qoling!😎 Admin: @Qoshish1
🅰🅰🅰🅰🅰🅰🅰👇 ✅1000 ta👤 - 25,000 so‘m💸 ✅2000 ta👤 - 50,000 so‘m💸 ✅3000 ta👤 - 75,000 so‘m💸 ✅4000 ta👤 - 100, Ming so‘m💸 ✅5000 ta👤- 125, Ming so‘m💸 ✅10,000 ta👤- 250, Ming so'm😀 🅰🅰🅰🅰🅰🅰⚫️⚫️⚫️ 👥Buyurtma berish: 👤@qoshish1 👤@kanalga_odam_qoshish_admini
✏️✏️✏️✏️✏️✏️ Faqat 3kun super aksiya kanallarga 100% uzbek odam aktiv qo'shamiz ular siz va bizga o'xshagan odamlar qo'shiladi ✅ 1000 tasi =100 ming 😍 10.000 tasi = 900 ming 😍 Diqqat aksiyaga ulgurib qoling!😎 Admin: @Qoshish1
Channel photo updated
😍😍😍 @Bolalar_bolajonlar_chaqaloqlar
😅😍 @Bolalar_bolajonlar_chaqaloqlar
😁😅 @Bolalar_bolajonlar_chaqaloqlar
😍😍😍 Do'stlaringizga ham ulashing https://t.me/Bolalar_bolajonlar_chaqaloqlar
Qanday shirin!)) 🥰👍❤️ Do'stlaringizga ham ulashing https://t.me/Bolalar_bolajonlar_chaqaloqlar
Два чудесных МК Do'stlaringizga ham ulashing https://t.me/Bolalar_bolajonlar_chaqaloqlar
🧸😅 https://t.me/Bolalar_bolajonlar_chaqaloqlar
Showing the 12 most recent of 20 posts we hold for @uzbek_ozbek_odam_qoshish. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Узбек одам кушиш” (@uzbek_ozbek_odam_qoshish), 116 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/uzbek_ozbek_odam_qoshish.
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.