Telegram RegisterThe public register of Telegram
Telegram profile photo for Taqvo TV | Расмий канал

Channel

Taqvo TV | Расмий канал

@taqvotvofficial

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,669subscribers

+18 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001636571661
TypeChannel
Username@taqvotvofficial
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/taqvotvofficial

Topic

Religion — 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 17 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

1,6511,6711,6616 August 2026 — 1,651 subscribers6 August 2026 — 1,651 subscribers10 August 2026 — 1,657 subscribers14 August 2026 — 1,660 subscribers17 August 2026 — 1,663 subscribers20 August 2026 — 1,665 subscribers26 August 2026 — 1,663 subscribers2 September 2026 — 1,659 subscribers7 September 2026 — 1,661 subscribers11 September 2026 — 1,671 subscribers18 September 2026 — 1,669 subscribers1,6696 August 202618 September 2026
11 measurements spanning 43 days, net +18. 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 1,648–1,674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 22:381,669-2
11 Sept 2026, 10:391,671+10
7 Sept 2026, 03:001,661+2
2 Sept 2026, 06:041,659-4
26 Aug 2026, 23:571,663-2
20 Aug 2026, 10:331,665+2
17 Aug 2026, 13:451,663+3
14 Aug 2026, 05:371,660+3
10 Aug 2026, 14:411,657+6
6 Aug 2026, 17:451,651no change
6 Aug 2026, 17:341,651first reading

Engagement

22 posts held, back to 21 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

115 reactions across 22 posts, in 5 distinct kinds. The most used accounts for 65.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7565.2%
👍3530.4%
👏21.74%
😢21.74%
🥰10.87%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 22 of the 22 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 115 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 21 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 05:50 UTC287 views7 reactionsread 7 August 2026
Photo

Жума айёмингиз муборак бўлсин! Аллоҳ таоло бу улуғ кунда қилган дуоларингизни ижобат, ибодатларингизни қабул айласин. Хонадонингиздан файзу барака, қалбингиздан иймон нури ва ҳаётингиздан хотиржамлик аримасин. Сизга ва яқинларингизга мустаҳкам соғлиқ, ҳалол ризқ ҳамда икки дунё саодатини насиб этсин! Жума муборак, азиз диндошим! Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

5👏2

6 Aug 2026, 20:35 UTC330 views4 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 7-август, жума Ҳижрий: 1448 йил 24-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:59 Қуёш: 05:47 Ишроқ: 06:02* Зуҳо: 09:02* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:15* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган. Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

4

5 Aug 2026, 22:35 UTC534 views3 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 6-август, пайшанба Ҳижрий: 1448 йил 23-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:58 Қуёш: 05:46 Ишроқ: 06:01* Зуҳо: 09:01* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:15* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган. Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

👍21

4 Aug 2026, 22:33 UTC556 views6 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 5-август, чоршанба Ҳижрий: 1448 йил 22-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:57 Қуёш: 05:45 Ишроқ: 06:00* Зуҳо: 09:00* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:15* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган.

6

3 Aug 2026, 22:32 UTC610 views4 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 4-август, сешанба Ҳижрий: 1448 йил 21-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:55 Қуёш: 05:44 Ишроқ: 05:59* Зуҳо: 09:00* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:14* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган.

4

2 Aug 2026, 22:34 UTC670 views6 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 3-август, душанба Ҳижрий: 1448 йил 20-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:54 Қуёш: 05:43 Ишроқ: 05:58* Зуҳо: 09:00* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:14* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган.

👍42

1 Aug 2026, 22:20 UTC716 views4 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 2-август, якшанба Ҳижрий: 1448 йил 19-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:52 Қуёш: 05:42 Ишроқ: 05:57* Зуҳо: 08:59* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:13* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган. Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

2👍2

1 Aug 2026, 00:46 UTC599 views4 reactionsread 7 August 2026
Photo

Бухоро вилояти учун 2026 йил АВГУСТ ойи намоз вақтлари. Аллоҳ таоло бундай марҳамат қилади: إِنَّ الصَّلاَةَ كَانَتْ عَلَى الْمُؤْمِنِينَ كِتَابًا مَّوْقُوتًا "Албатта, намоз мўминларга вақти тайин этилган ва (фарз деб) битилгандир (Нисо сураси, 103-оят). Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

4

1 Aug 2026, 00:32 UTC605 views10 reactionsread 7 August 2026
Photo

🌅 Тонг — барака вақти. Расулуллоҳ ﷺ: «Эй Аллоҳ! Умматимнинг эрталабки ишларига барака бергин», деб дуо қилганлар. (Абу Довуд, Термизий, Ибн Можа) Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

8👍2

31 Jul 2026, 22:33 UTC699 views5 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 1-август, шанба Ҳижрий: 1448 йил 18-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:51 Қуёш: 05:41 Ишроқ: 05:56* Зуҳо: 08:59* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:12* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган. Тақво ҳамиша ҳамроҳингиз бўлсин! https://t.me/taqvotvofficial

👍41

29 Jul 2026, 19:47 UTC809 views8 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 30-июль, пайшанба Ҳижрий: 1448 йил 16-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:48 Қуёш: 05:39 Ишроқ: 05:54* Зуҳо: 09:04* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:11* — *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган.

👍62

28 Jul 2026, 22:33 UTC827 views7 reactionsread 7 August 2026
Photo

Ҳудуд: Бухоро шаҳри (Бухоро вилояти) Сана: 2026 йил 29-июль, чоршанба Ҳижрий: 1448 йил 15-сафар Мазҳаб: Ҳанафий Субҳ: (эҳтиётини инобатга олиб белгиланган) 03:47 Қуёш: 05:38 Ишроқ: 05:53* Зуҳо: 09:04* Аввобийн: Шом намозидан кейин* Таҳажжуд: 01:11* *Нафл намозлари – ҳадисларда келган афзал вақтлар инобатга олинган ҳолда белгиланган.

7

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

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 6 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.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Taqvo TV | Расмий канал” (@taqvotvofficial), 1,669 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/taqvotvofficial.

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.