18. AUGUST . 2026yil. 19. RABI’ AL-AVVAL . 1448yil. Seshanba. Toshkent vaqti bilan. 04:09 BOMDOD. 05:35 QUYOSH. 12:32 PESHIN. 17:17 ASR. 19:20 SHOM 20:41 XUFTON. @Namoz_vaqti
❤426

Channel
@namoz_vaqti
On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
131,840subscribers
+302 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001369049891 |
|---|---|
| Type | Channel |
| Username | @namoz_vaqti |
| Created | 3 April 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/namoz_vaqti |
Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
112,000 average views per post against 131,828 subscribers — an engagement rate of 84.8%. Across the 6,910 registered channels in the same cohort — 100,000–316,200 subscribers — the middle half sit between 2.09% and 14.2%, with a median of 5.94%.
| Window | 30 days (19 July 2026 – 18 August 2026) |
|---|---|
| Posts measured | 36 of 36 published in the window (0 exact, 36 rounded by Telegram) |
| Views totalled | 4,023,200 |
| Mature posts only | 86.4% over 35 posts read at least 24h after publication |
| Subscribers | 131,828 measured 17 August 2026 |
| Cohort | b100000 · 6,910 channels · p10 0.682% · p25 2.09% · p50 5.94% · p75 14.2% · p90 27.3% |
| Position in cohort | 99.711th percentile · 14.3× the cohort median |
| Uncertainty | ±0.037% of the figure, from Telegram’s rounding |
| Post language | Belarusian · 63.6%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 18 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 18:42 | 131,840 | +12 |
| 17 Aug 2026, 20:28 | 131,828 | -21 |
| 16 Aug 2026, 19:48 | 131,849 | +21 |
| 15 Aug 2026, 05:27 | 131,828 | +21 |
| 14 Aug 2026, 01:16 | 131,807 | +50 |
| 12 Aug 2026, 21:08 | 131,757 | +32 |
| 11 Aug 2026, 20:52 | 131,725 | +64 |
| 10 Aug 2026, 18:24 | 131,661 | +64 |
| 9 Aug 2026, 15:12 | 131,597 | +7 |
| 8 Aug 2026, 13:58 | 131,590 | -30 |
| 7 Aug 2026, 16:36 | 131,620 | +64 |
| 6 Aug 2026, 14:55 | 131,556 | +18 |
| 6 Aug 2026, 08:48 | 131,538 | first reading |
36 posts held, back to 25 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 28 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 August 2026 |
|---|---|
| Posts held | 36 (25 July 2026 – 17 August 2026) |
| Views total | 4,023,200 |
| Reactions total | 24,386 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Aug 2026, 10:09 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.
23,006 reactions across 35 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23,006 | 100.0% |
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 36 of the 36 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 24,386reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 25 July 2026 to 17 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.
18. AUGUST . 2026yil. 19. RABI’ AL-AVVAL . 1448yil. Seshanba. Toshkent vaqti bilan. 04:09 BOMDOD. 05:35 QUYOSH. 12:32 PESHIN. 17:17 ASR. 19:20 SHOM 20:41 XUFTON. @Namoz_vaqti
❤426
17. AUGUST . 2026yil. 18. RABI’ AL-AVVAL . 1448yil. Dushanba. Toshkent vaqti bilan. 04:07 BOMDOD. 05:34 QUYOSH. 12:32 PESHIN. 17:18 ASR. 19:21 SHOM 20:43 XUFTON. @Namoz_vaqti
❤586
16. AUGUST . 2026yil. 17. RABI’ AL-AVVAL . 1448yil. Yakshanba. Toshkent vaqti bilan. 04:06 BOMDOD 05:33 QUYOSH. 12:32 PESHIN. 17:19 ASR. 19:23 SHOM 20:45 XUFTON. @Namoz_vaqti
❤557
15. AUGUST . 2026yil. 16. RABI’ AL-AVVAL . 1448yil. Shanba. Toshkent vaqti bilan. 04:04 BOMDOD. 05:32 QUYOSH. 12:32 PESHIN. 17:20 ASR. 19:24 SHOM 20:46 XUFTON. @Namoz_vaqti
❤615
14. AUGUST . 2026yil. 15. RABI’ AL-AVVAL . 1448yil. Juma. Toshkent vaqti bilan. 04:03 BOMDOD 05:31 QUYOSH. 12:32 PESHIN. 17:21 ASR. 19:25 SHOM 20:48 XUFTON. @Namoz_vaqti
❤631
13. AUGUST . 2026yil. 14. SAFAR . 1448yil. Payshanba. Toshkent vaqti bilan. 04:02 BOMDOD 05:30 QUYOSH. 12:33 PESHIN. 17:22 ASR. 19:26 SHOM 20:50 XUFTON. @Namoz_vaqti
❤679
12. AUGUST . 2026yil. 29. SAFAR . 1448yil. Chorshanba. Toshkent vaqti bilan. 04:00 BOMDOD. 05:29 QUYOSH. 12:33 PESHIN. 17:23 ASR. 19:28 SHOM. 20:51 XUFTON. @Namoz_vaqti
❤601
НАМОЗНИНГ КЎЗГА ФОЙДАСИ Германияда бир кўз шифокори қабулига келган мусулмон йигитни текширади. Текшириб бўлиб унга савол беради: - Сен намоз ўқийсанми? Йигит: - Дўхтир, менинг кўзимдаги дард билан намознинг қандай алоқаси бор. Мендан намоз ўқиш-ўқимаслигимни сўраяпсиз? Германиялик шифокор айтадики: - Агар сен намоз ўқисанг, ўқиб бўлиб икки томонга салом бераётгандаги ҳаракатни қилганингда бу касаллик сенда бўлмасди…
❤812
11. AUGUST . 2026yil. 28. SAFAR . 1448yil. Seshanba. Toshkent vaqti bilan. 03:59 BOMDOD. 05:28 QUYOSH. 12:33 PESHIN. 17:24 ASR. 19:29 SHOM. 20:53 XUFTON. @Namoz_vaqti
❤522
Ҳадис ва ҳикматларга суянган ҳолда Қиёмат аломатларидан 50 тасини тасбеҳ тимсол териб, туздик 1. Охир замон пайғамбари - жанобимиз Муҳаммад соллаллоҳу алайҳи васаллам дунёга келдилар. 2. Аллоҳ таборака ва таоло олимларни олиб қўйиб, ўз илмини кўтаради. 3. Имонсизлар кўпайиб, Қуръондан бир расм, Исломдан бир исм, мусулмондан бир жисм қолади. 4. Миноралар кўпаяди, масжидлар черков каби безатилади. 5. Камбағаллар намоз…
❤716
10. AUGUST . 2026yil. 27. SAFAR . 1448yil. Dushanba. Toshkent vaqti bilan. 03:58 BOMDOD. 05:27 QUYOSH. 12:33 PESHIN. 17:24 ASR. 19:30 SHOM 20:55 XUFTON. @Namoz_vaqti
❤479
Таҳоратда бошга масҳ тортишнинг фойдаси Инсоннинг бош чаноғида, бош суягида бир жой бор, бу анъанавий тиббиётда "яфуқ", замонавий тиббиётда эса "сагиттал бўғини" (Sagittal suture) деб аталади. Бошнинг айнан шу ери мияда қуруқлик, сувсизланиш, уйқусизлик, қулоқларда ғувиллаш, шовқин, ва юракда ғашлик, безовталикни келиб чиқишига сабаб бўлади. Бунинг учун табиий ва самарали ечим эса, таҳорат вақтида бошга масҳ торти…
❤733
Showing the 12 most recent of 36 posts we hold for @namoz_vaqti. 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.
Citation-graph rank — 92,170 of 1,549,704entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 9 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.
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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 13 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Namoz vaqti” (@namoz_vaqti), 131,840 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/namoz_vaqti.
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.