🕺ASADBEK TOURNAMENT 🕺 Sovrin Jamg'armasi: 500.000so'm 🟢Sanasi: 06.08.2026 🟢Vaqti: 20:00🇺🇿 : 18:00🇷🇺 🟢Vaqti: 23:00🇺🇿 : 21:00🇷🇺 🟢Jamoalar soni: 18 🟢Stage: 1/2 🟢Slot narxi: 8.000so'm (80₽) 🟢Praxod Top3<FINAL 🟢Garant: ASAD GARANT 🟢Strem bor 100%📹 🟢FAST REZ + PMCO + PING 20 🔔Sotib olish: @Asadbek39_58 💬ASADBEK TOURNAMENT

Channel
ASADBEK UC SERVIS
@ASADBEK_UC_SERVISI
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
356subscribers
-41 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002440709198 |
|---|---|
| Type | Channel |
| Username | @ASADBEK_UC_SERVISI |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/ASADBEK_UC_SERVISI |
Topic
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 22 September 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 |
|---|---|---|
| 12 Sept 2026, 19:19 | 356 | -9 |
| 5 Sept 2026, 03:40 | 365 | -6 |
| 28 Aug 2026, 07:18 | 371 | -13 |
| 21 Aug 2026, 09:12 | 384 | -8 |
| 15 Aug 2026, 04:14 | 392 | -5 |
| 8 Aug 2026, 05:50 | 397 | no change |
| 7 Aug 2026, 10:44 | 397 | first reading |
Engagement
20 posts held, back to 22 April 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Posted without readable text
➡️20:00 1 DONA SLOT QOLGAN ➡️ETAP 1/2 800.000uzs ➡️SLOT: #skidka 10k ➡️📹 STREAM BULADI ➡️MAX KAMANDA 20 TA ➡️MUROJAAT:@Asadbek39_58 ❗️ FAST REZ + PMCO + TOP5 FRAGER HAM CHIQARILADI ❗️ERTAGA FINAL
📣ASADBEK TOURNAMENT S70📣 💵 Sovrin Jamg'armasi: 800.000 so’m ➡️Sanasi: 06.07.2026 (bugun) ➡️Vaqti: 20:00🇺🇿 18:00 🇷🇺 ➡️Vaqti: 23:00🇺🇿 21:00 🇷🇺 ➡️Jamoalar soni: 18 ➡️GARANT: Asad garant ➡️Stage: 1/2 ➡️PRAXOD: TOP3--> FINAL ➡️VIP SLOT: 15.000uzs✅ ➡️SOTIB OLISH: @ASADBEK39_58 ✅ ❗️OXIRGI KUN ERTAGA FINAL STREAM BOR 📹 FINALDA 💬ASADBEK TOURNAMENT
➡️20:00 1 DONA SLOT QOLGAN ➡️ETAP 1/2 800.000uzs ➡️SLOT: #skidka 13k ➡️📹 STREAM BULADI ➡️MAX KAMANDA 20 TA ➡️MUROJAAT:@Asadbek39_58 ❗️HOST UZIM HECH QANAQA MOOMMO BUMEDI ❗️ FAST REZ + PMCO + TOP5 FRAGER HAM CHIQARILADI
📣ASADBEK TOURNAMENT S70📣 💵 Sovrin Jamg'armasi: 800.000 so’m ➡️Sanasi: 04.07.2026 (bugun) ➡️Vaqti: 20:00🇺🇿 18:00🇷🇺 ➡️Vaqti: 23:00🇺🇿 21:00 🇷🇺 ➡️Jamoalar soni: 18 ➡️GARANT: Asad garant ➡️Stage: 1/2 ➡️PRAXOD: TOP3--> FINAL ➡️VIP SLOT: 15.000uzs✅ ➡️SOTIB OLISH: @ASADBEK39_58 ✅ STREAM BOR 📹 FINALDA 💬ASADBEK TOURNAMENT
📣ASADBEK TOURNAMENT S70📣 💵 Sovrin Jamg'armasi: 800.000 so’m ➡️Sanasi: 03.07.2026 (bugun) ➡️Vaqti: 20:00🇺🇿 18:00🇷🇺 ➡️Vaqti: 23:00🇺🇿 21:00 🇷🇺 ➡️Jamoalar soni: 18 ➡️GARANT: Asad garant ➡️Stage: 1/2 ➡️PRAXOD: TOP3--> FINAL ➡️VIP SLOT: 15.000uzs✅ ➡️SOTIB OLISH: @ASADBEK39_58 ✅ STREAM BOR 📹 FINALDA 💬ASADBEK TOURNAMENT
120uc - 22.500
60uc - 11.000
660uc - 108.000 325uc - 55.000 @Z7uhriddin
Aksiya 8100 uc 1.045.000 @Z7uhriddin
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @ASADBEK_UC_SERVISI. 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.
Forward network
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.
Mentions
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“ASADBEK UC SERVIS” (@ASADBEK_UC_SERVISI), 356 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/ASADBEK_UC_SERVISI.
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.