Telegram RegisterThe public register of Telegram

Channel

NAVBAHOR NEWS

@NAVBAHORNEWS

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

71,761subscribers

-2,908 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001268278104
TypeChannel
Username@NAVBAHORNEWS
DescriptionНавбаҳор футбол клубининг янгиликлари Мурожаат учун: @FCNAVBAHOR_BOT Реклама: @ASADBEK_ERGASHEV
Created28 September 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/NAVBAHORNEWS

Growth

71,76174,66973,2156 August 2026 — 74,669 subscribers7 August 2026 — 74,632 subscribers7 August 2026 — 74,661 subscribers8 August 2026 — 74,531 subscribers9 August 2026 — 74,421 subscribers11 August 2026 — 74,255 subscribers12 August 2026 — 74,009 subscribers12 August 2026 — 73,899 subscribers14 August 2026 — 71,761 subscribers6 August 202614 August 2026
9 measurements spanning 8 days, net -2,908. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 71,325–75,105 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:0471,761-2,138
12 Aug 2026, 23:2873,899-110
12 Aug 2026, 00:2274,009-246
11 Aug 2026, 01:4574,255-166
9 Aug 2026, 23:3174,421-110
8 Aug 2026, 21:1474,531-130
7 Aug 2026, 23:2774,661+29
7 Aug 2026, 00:3674,632-37
6 Aug 2026, 09:4674,669first reading

Engagement

72 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.1%
avg views ÷ 71,761 subscribers
Avg views / post
26,600
72 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
72
of 72 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held72 (5 August 202614 August 2026)
Views total1,916,420
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 09:08 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
5,130
Videos
2,450
Links
2,060

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
50m 15s
Average length
2m 11s

Measured directly from 23 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.

Recent posts

14 Aug 2026, 05:54 UTC≈13,000 viewsread 14 August 2026
Video

Чипталарни фақат кассалардан харид қилинг! 30 000 сўмдан қиммат чипталарни харид қилманг! 🔵 @NAVBAHORNEWS

14 Aug 2026, 05:00 UTC≈15,600 viewsread 14 August 2026
Video

🔵 Навбаҳор - Бунёдкор 🔵 ўйини учун чипталар сотуви бугун ҳам давом этмоқда. Чипталарни ўйиндан аввал стадион атрофидан ўз нархида харид қилишингиз мумкин. 🎫 Чипта нархи: 30 000 сўм 📆 Ўйин вақти: 14 август | 19:00 🔵 @NAVBAHORNEWS

14 Aug 2026, 02:07 UTC≈22,200 viewsread 14 August 2026
Photo

#БУГУН_ФУТБОЛ 🤩 ⚽️Суперлига | 17-тур 🔵Навбаҳор - Бунёдкор🔵 📆14 август | Жума ⏰19:00 🏟Навбаҳор стадиони 🎫Чипта нархи: 30 000 сўм 🔵 @NAVBAHORNEWS

13 Aug 2026, 17:50 UTC≈25,200 viewsread 14 August 2026
Photo

🔵 Навбаҳор - Бунёдкор 🔵 ўйини олдидан турнир жадвали 📊 🔵 @NAVBAHORNEWS

13 Aug 2026, 14:36 UTC≈25,500 viewsread 14 August 2026
Video

Эртага яна Наманганда футбол байрами 🔥 🔵 @NAVBAHORNEWS

13 Aug 2026, 10:20 UTC≈28,600 viewsread 14 August 2026
Video

Чипталар сотуви авжида! Эртага мавсум рекордини биргаликда ўрнатамиз! 🔥 Сўнгги йилларда мухлислар ташрифи бўйича мавсум рекордлари: 🎥 2018. Навбаҳор - Локомотив 2:0 | 25 300 🎥 2019. Навбаҳор - Сўғдиёна 3:1 | 25 727 🎥 2020. Навбаҳор - Локомотив 2:0 | 25 328 🎥 2021. Навбаҳор - Насаф 0:0 | 19 358 🎥 2022. Навбаҳор - Бунёдкор 2:1 | 26 231 🎥 2023. Навбаҳор - Пахтакор 1:2 | 25 216 🎥 2024. Навбаҳор - Нефтчи 1:0 | 22 350 🎥 2

13 Aug 2026, 10:20 UTC≈21,700 viewsread 14 August 2026
Photo

🐉 Endi Xitoy devori ham to'siq emas! BRB mobil ilovasida "Xitoyga o'tkazmalar" xizmati ishga tushdi. Endi mablag'ni to'g'ridan-to'g'ri: ✅ Alipay elektron hamyoniga ✅ WeChat Pay elektron hamyoniga ✅ Xitoyda chiqarilgan UnionPay kartalariga yuborishingiz mumkin. Yangi xizmat Xitoy bilan moliyaviy aloqalarni yanada qulay yo'lga qo'yishga yordam beradi — biznes to'lovlaridan tortib Xitoy fuqarolariga pul o'tkazmalarig

13 Aug 2026, 08:13 UTC≈21,500 viewsread 14 August 2026
Photo

⚽️🇺🇿 Бугундан 17-тур старт олади 🔥 🔵 @NAVBAHORNEWS

13 Aug 2026, 08:13 UTC≈26,200 viewsread 14 August 2026
Video

🔥 361° SPORT’DA DAXSHAT CHEGIRMALAR! 🔥 Magazinimizdagi barcha sifatli va original sport kiyimlari hamda krossovkalarga 30% dan 50% gacha chegirma e’lon qilamiz! 📅 Aksiya muddati: 13-avgustdan 16-avgustgacha ⚠️ Mahsulotlar soni chegaralangan! 👉 Do'stlaringizga ham ulashing! ⏰ 8:30 — 00:00 (24/7) 📥 @361sportadmin 📲 @s361sportuz 📌 Instagram 📞 +998990952020 📍 Namangan shahar, Boburshox ko’chasi, 88/

13 Aug 2026, 06:43 UTC≈25,800 viewsread 14 August 2026
Video

🔵 Навбаҳор - Бунёдкор 🔵 ўйини учун чипталар сотуви Марказий ўйингоҳ кассаси, Чорсу бозори ичида ва Сардоба кўприк олдида давом этмоқда ✅ 🎫 Чипта нархи: 30 000 сўм 📆 Ўйин вақти: 14 август | 19:00 🔵 @NAVBAHORNEWS

13 Aug 2026, 06:43 UTC≈23,100 viewsread 14 August 2026
Photo

Changan UNI-T — endi yanada qulay shartlarda! 🔥 💳 Oylik to‘lov: 4 200 000 so‘m 📅 Muddat: 40 oygacha ✅ Yillik stavka: 0% Zamonaviy dizayn, qulaylik va ilg‘or texnologiyalar — barchasi Changan UNI-T da. ⚡️ Shoshiling va qulay shartlardan foydalaning! 📍 Changan Namangan 📞 +998555009006

12 Aug 2026, 08:44 UTC≈32,300 viewsread 14 August 2026
Photo

🔵 Навбаҳор - Бунёдкор 🔵 ўйини учун чипталар Марказий ўйингоҳ кассаси, Чорсу меҳмонхонаси атрофи, Лола Жаҳон бозори, Сардоба Мегаполис олдида сотувга чиқди ✅ 🎫 Чипта нархи: 30 000 сўм 📆 Ўйин вақти: 14 август | 19:00 🔵 @NAVBAHORNEWS

Showing the 12 most recent of 72 posts we hold for @NAVBAHORNEWS. 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.

Posts edited after publishing

@NAVBAHORNEWS edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 August 2026
Most recent edit
11 August 2026

Citation-graph rank

Citation-graph rank — 89,919 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

Named by 11 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Namangan yangiliklari
@namanganlive24 · 133,991
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 13 August 2026
Namanganliklar.Uz | Расмий
@namanganliklar_uz · 510,042
Telegram ranks this channel #44 of 59 here — alongside 58 others — read 9 August 2026
NAMANGANLIKLAR
@NAMANGANLIKLAR · 116,121
Telegram ranks this channel #47 of 55 here — alongside 54 others — read 14 August 2026
🎥UZvideo | Расмий
@vodiy_times · 119,864
Telegram ranks this channel #61 of 63 here — alongside 62 others — read 14 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Навбахор (ru.wikipedia.org)
“…Официальный сайт клуба — pfcnavbahor.uz] * [https://t.me/NAVBAHORNEWS Официальный канал клуба в Telegram — t.me/fcnavbahor] * [https://www.instagram.com/fcnavbahor_/…”
read 9 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“NAVBAHOR NEWS” (@NAVBAHORNEWS), 71,761 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/NAVBAHORNEWS.

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.