Pakhtakor FC 1. Bahtimurod Hakimov @Bahtimurod Kapitan 2. Ramziddin Umarov Ramziddin_7 3. Farxod Rahimbabayev @itshop_manager1 4. Javlon Muhamedov @JAVA_9006 5. Jamshidbek Nosirov @do_a_barrel_roll 6. Jurabek Abdumannonov @leo2208 7. Javohir Shokirov @Muhammad_Javohir

Channel
Virtual Futbol Ligasi arhiv
@virfutligarhiv
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
15subscribers
+0 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 | -1001431325353 |
|---|---|
| Type | Channel |
| Username | @virfutligarhiv |
| Description | Virtual futbol ligasi jamoalar tarkibi, o'tkazilgan turnirlar natijalari, chempionlarga berilgan sovrinlar va hk. |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/virfutligarhiv |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:01 | 15 | no change |
| 7 Aug 2026, 00:43 | 15 | first reading |
Engagement
20 posts held, back to 23 August 2022 — 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 pageof 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 21 June 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 100
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Recent posts
Хасанбой ( @HasanboyAnorov ) Абдулатиф ( @AbdulatiF_ErgasheV ) Музаффархон ( @Khan_Respect01 ) Шерзод ( @the_sherxon_king ) Машхура ( @barbie_ocean )
1. Javlonbek Tojiyev(с)- @Java_navai1 2. Furqat Abdumo'minov- @Abdumumin9v 3. Omonjon Saliyev-@Omonjon_Saliyev 4. Zafarbek Kenjayev-@Zafa_Khenjayev 5. Umidjon Ibragimov- @ibragiimov_u 6. Lochinbek- @Lochinbek10 7. Shaxriyor- @Zizu_Shakhriyar
Kapitan kim
1. Шох (@ProudCityzen) 2. Аъзамхон (@azam2610) 3. Бахтиёр (@Meloman_R90) 4. Генахан (@GenaKhan95) 5. Бахтиёр 2107 (@Khamidullaev_07) 6. Азамат (@AAP_0510)
1. Хуршид Бахтияров ( капитан ) 2. Хасан Аскаров @Askarov86 3. Одил Махмудов @Makhmoodoff 4. Зухриддин Абдуллаев @ATZIMSH 5. Шерзод Мирзаев @Shera2101 6. Шавкат Ботиров @COYG7 7. Мамур Усмонов @MamurUsmonov
FUTMIND⚽️ Ergashboy (@Ergashboy_me) © Izzatbek ( @makhmudov1988) Nodirbek (@InshallahDiplomatiya) Hamidjon (@djhamid94) Jamshidbek (@AJamshid_01) Shoxrux (@Shokhxx18) Saylaw (@joldasbaevSaylaw15)
Жамоалар таркиби:
"Виртуал футбол чойхона КВИЗ" турнири регламенти 1. ТУРНИР ҲАҚИДА УМУМИЙ МАЪЛУМОТ 1.1. Турнир номланиши: Виртуал футбол лигаси ва Футбол чойхонаси каналлари ҳамкорлигидаги «ВИРТУАЛ ФУТБОЛ ЧОЙХОНА КВИЗ» жамоавий футбол заковати ва савол-жавоблар турнири 1.2. Турнирда иштирок этадиган барча қатнашчи ва жамоалардан ҳалол ўйин ва охиригача иштирокни кутиб қоламиз. 1.3. Турнирда футбол ичида, футбол атрофида, футбол …
5.ЖАВОБЛАР ҲАҚИДА: 5.1. Жамоаларнинг гуруҳларда берган жавоблари ҳисобланмайди. Фақатгина ҳакамга йўлланган бир вариантгина қабул қилинади. 5.2. Тўлдирувчи жавоблар, ўзгартириш киритилган жавоблар қабул қилинмайди. 5.3. Жавоблар рақамланган ҳолда жўнатиш зарур. Акс ҳолда балл қўйилмаслиги мумкин ва ушбу ҳолатда ҳеч бир эътироз қабул қилинмайди. 5.4. Тур натижалари 7 та саволдан сўнг ҳисобланиб эълон қилинади. 5.…
ЕВРОКУБОК ПЛЕЙ-ОФФ 5. Плей-оффда чорак финал ва ярим финал ўйинлари уй-сафар тизимида, финал ва 3-ўрин учун ўйин бир матч тизимида бўлиб ўтади. 6. Плей-оффда икки ўйин натижасига кўра дуранг бўлиб қолса, сафарда кўпроқ гол урган жамоа ютган ҳисобланади. 7. 2 ўйинда ҳам бир дуранг бўлиб қолса яна иккита қўшимча ўйин берилади (натижадан кейинги 24 соат ичида ўйналадиган 2 та ўйин). Шунда ҳам дуранг бўлиб қолса фақат ж…
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @virfutligarhiv. 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.
Handles this channel named that no longer answer
- Dead references
- 17
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 17
- vacant every time we have ever looked
@virfutligarhiv named 17 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Virtual Futbol Ligasi arhiv” (@virfutligarhiv), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/virfutligarhiv.
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.