Telegram RegisterThe public register of Telegram
Telegram profile photo for ХУТБЫ

Channel

ХУТБЫ

@hutba_doc

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

948subscribers

-13 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-1001937642625
TypeChannel
Username@hutba_doc
Created1 August 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/hutba_doc

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 19 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

948961954.57 August 2026 — 961 subscribers8 August 2026 — 961 subscribers14 August 2026 — 958 subscribers9 September 2026 — 954 subscribers19 September 2026 — 948 subscribers7 August 202619 September 2026
5 measurements spanning 43 days, net -13. 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 946–963 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:01948-6
9 Sept 2026, 20:40954-4
14 Aug 2026, 19:56958-3
8 Aug 2026, 00:47961no change
7 Aug 2026, 14:01961first reading

Engagement

20 posts held, back to 16 September 2023the 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 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 Jul 2026, 18:41 UTC370 viewsread 8 August 2026
File

Отдых в Исламе Шейх ‘Абд уль-Бари ас-Субейти

2 May 2026, 13:48 UTC≈1,150 viewsread 8 August 2026
File

Нрав верующего Шейх Халид Исмаиль

12 Apr 2026, 14:27 UTC≈1,530 viewsread 8 August 2026
File

Хадж - столп Ислама Шейх Сулейман ар-Рухейли

17 Mar 2026, 10:51 UTC≈2,170 viewsread 8 August 2026
File

Мы не теряем награды тех, кто совершал добро Шейх ‘Абд уль-Бари ас-Субейти

19 Feb 2026, 15:31 UTC≈6,880 viewsread 8 August 2026
File

Содействие от Аллаха Шейх Абдурраззак аль-Бадр

12 Feb 2026, 23:15 UTC≈9,240 viewsread 8 August 2026
File

Достоинства месяца Рамадан Шейх Абдурраззак аль-Бадр

15 Jan 2026, 22:16 UTC≈2,930 viewsread 8 August 2026
File

Познал ли ты Аллаха? Шейх ‘Абд уль-Бари ас-Субейти

11 Dec 2025, 13:33 UTC≈4,450 viewsread 8 August 2026
File

Великая ответственность известных людей Шейх ‘Абд уль-Бари ас-Субейти

21 Nov 2025, 08:52 UTC≈3,320 viewsread 8 August 2026
File

Остерегайтесь зависти Шейх Халид Исмаиль

25 Aug 2025, 04:32 UTC≈3,440 viewsread 8 August 2026
File

Последние ночи Рамадана Шейх ‘Абд уль-Бари ас-Субейти

18 Aug 2025, 01:54 UTC≈3,440 viewsread 8 August 2026
File

Краткая история пророка Шейх ‘Абд уль-Бари ас-Субейти

6 Jul 2025, 16:07 UTC≈3,690 viewsread 8 August 2026
File

Признание в грехе Шейх ‘Абд уль-Бари ас-Субейти

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

Mentions

Named by 2 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.

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

“ХУТБЫ” (@hutba_doc), 948 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hutba_doc.

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.