Channel
@WR_Qoidalar_2026
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
11subscribers
+0 since we began measuring on 16 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004485971109 |
|---|---|
| Type | Channel |
| Username | @WR_Qoidalar_2026 |
| Description | Wild Rift Uzbekistan Final Turnir Qoidalari. |
| Created | 16 July 2026 — measured — dated from the channel’s first post |
| First recorded | 16 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/WR_Qoidalar_2026 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 13:22 | 11 | no change |
| 16 Sept 2026, 12:47 | 11 | first reading |
6 posts held, back to 16 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 6 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 16 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
Shaxsa oid ma'lumotlar biz tamonlama himoyalash kafolati yuklatimaydi, jamoa sardoriga ishonch bo'lsa bering. - Sizning shaxsiy ma'lumotlaringiz biz tamonlama 3 chi shaxslarga berish va ularni tahlil qilish uchun huquqiy baza yo'q, biroq biz ma'lumotlarizga javob bermaymiz. - Yagona OneID tizimi orqali kredit yoki iqtisodiy shartnomalarga taqiq qo'yishingiz mumkin.
// qo'shimcha qoidalar Jamoalar sardorlari: 7.0 Jamoa sardorlari o'z jamoasi uchun to'liq javobgar. 7.1 Jamoa sardorlari berlashuv vaqtida faol bo'lishi va jamoaning berlashuv aniq belgilangan sana va soatiga tayyor tutishi kerak. 7.2 Jamoa sardorlari, o'z jamoasi bilan to'liq aloqaga ega bo'lishi kerak, telefon raqam hamda pasport ma'lumotlari. 7.3 Jamoa sardori jamoa a'zolarini mustaqil tanlash imkoniyatiga ega, …
Quydagi videoda qanday qilib bank to'g'risida ma'lumot olish mumkinligi aks etilgan. MFO, STIR va Hisob raqami qanday oliniladi, va u yopiq ma'lumot hisoblanadimi? - Yo'q, har bir bank o'z ma'lumotlarini ochiqlaydi va bank raqamiga telefon qilib so'rasangiz bo'ladi. (uning uchun shaxsni tastidlash ham kerak emas) Shaxsiy ma'lumot sifatida bulardan nima maqsadda foydalansa bo'ladi, misol kredit olish yoki hokazo? …
Savollarga javob tariqasida ushbu ekran skrini qo'shildi: MFO (bank), STIR (bank), Hisob rqam (Bank), Plataik raqam (fuqaro), Isim Sharif - Faqatgina yutgan jamoa ishtrokchilari uchun so'raladi. Ro'yhatga olish va qatnashish uchun faqat: Ism Sharif Pasport seriya Telefon raqam. DIQQAT: - Yutgan jamoa uchun mablag' jo'natilvotgan payt, yutgan jamoa ishtirokchilari ma'lumotlari - ro'yhatga olingan ma'lumotlar bilan t…
Wild Rift Uzbekistan Turnir 2026 Final Ro'yhatga olish: 1. Siz O'zbekiston Respublikasi fuqarosi bo'lishingiz kerak. 2. Qatnashish yoshi 16 yoshdan kam bo'lishi kerak emas. 3. Ro'yhatdan o'tish faqatgina jamoa sardorlari orqali amalga oshiriladi. 4. O'zbekiston fuqarolari jinsi millati dan qattiy nazar qatnashish huquqiga ega bo'ladilar. 5. Sovrin uchun ajratilgan mablag' O'zbekiston so'mida taqdim etiladi va s…
Channel created
Showing the 6 most recent of 6 posts we hold for @WR_Qoidalar_2026. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
“WR Qoidalar 2026” (@WR_Qoidalar_2026), 11 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/WR_Qoidalar_2026.
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.