🚖1268🚖 дустлар хаммамизга муборак болсин
Signed Шох Султон 7777

Channel
@Uchkurgan_taxi1268
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
11subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001356176735 |
|---|---|
| Type | Channel |
| Username | @Uchkurgan_taxi1268 |
| Created | 28 March 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Uchkurgan_taxi1268 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 07:46 | 11 | no change |
| 7 Aug 2026, 20:02 | 11 | first reading |
20 posts held, back to 24 January 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 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 5 August 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
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.
🚖1268🚖 дустлар хаммамизга муборак болсин
Signed Шох Султон 7777
🚖1268🚖
Signed Шох Султон 7777
🎶 To'liq Mp3 pastda ⏬
Signed Шох Султон 7777
🚖1268🚖
Signed Шох Султон 7777
Video, posted without a caption
Signed Шох Султон 7777
🚖1268🚖UCHQORGON TAXI
Signed Шох Султон 7777
🚖1268🚖EXRESS TAXI UCHQORGON🚖🚖
Signed Шох Султон 7777
РАМАЗОНУ ШАРИФНИ СУНГИ Жумаси муборак бўлсин! КЕЛАСИ РАМАЗОНГА ОЛЛОХИМ ХАММАМИЗНИ ЕТКАЗСИН🤲🤲🤲 Бугун шундай Жума бўлсинки: Афв этилмаган БАНДА; Қабул бўлмаган ДУО; Даф бўлмаган БАЛО; Шифо топмаган ХАСТА; Ҳузур топмаган ҚАЛБ; АЛЛОҲ демаган "ТИЛ" қолмасин! ❗️Айёмингиз муборак бўлсин, @uchkurgan_taxi1268
Signed Шох Султон 7777
Photo, posted without a caption
Signed Шох Султон 7777
#VAKANSIYA #ELON #ishbor DIQQAT ELON VAKANSIYA EXPRESS TAXI 1268 TAXI XIZMATIGA QIZLARNI OPERATORLIKGA ISHGA TAKLIF QILAMIZ MUROJAT UCHUN TELEFON +998992298000 TELEGRAMDAN MUROJAT OZODBEK BIZNING GURUH EXPRESS TAXI 1268 BIZNING KANAL EXPRESS TAXI 1268 UCHQORGONLIKLAR KANALIGA OBUNA BO'LING
Signed EXPRESS TAXI
🏡 #ХовлиСотилади! 📐 Сотих 2 ⚡️ Электр 💦 Сув 💰 Нархи- (Келишамиз) 📁 Хужжатлари бор 📌Манзил: uzTex kotejlari tarafda 📞 +998945042705 Каналга обуна булинг: https://t.me/uy_bozor_uchqorgon
Signed Ozodbek
#VAKANSIYA #ELON #ishbor DIQQAT ELON VAKANSIYA EXPRESS TAXI 1268 TAXI XIZMATIGA QIZLARNI OPERATORLIKGA ISHGA TAKLIF QILAMIZ MUROJAT UCHUN TELEFON +998992298000 TELEGRAMDAN MUROJAT OZODBEK BIZNING GURUH EXPRESS TAXI 1268 BIZNING KANAL EXPRESS TAXI 1268 UCHQORGONLIKLAR KANALIGA OBUNA BO'LING
Signed EXPRESS TAXI
Showing the 12 most recent of 20 posts we hold for @Uchkurgan_taxi1268. 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.
@Uchkurgan_taxi1268 named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Express taxi Uchqo‘rg‘on” (@Uchkurgan_taxi1268), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Uchkurgan_taxi1268.
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.