Telegram RegisterThe public register of Telegram
Telegram profile photo for تذكير بـ الحوقلة و صلاه ع النبي

Channel

تذكير بـ الحوقلة و صلاه ع النبي

@uilal

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,508subscribers

-11 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-1001427792184
TypeChannel
Username@uilal
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/uilal

Topic

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 11 August 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hiiiaah/574415 Aug 2026, 01:55 UTC@uilal/120304 · this entry6 Aug 2026, 01:54 UTC1.0024 hours
@uilal/120307 · this entry6 Aug 2026, 02:10 UTC@hiiiaah/574856 Aug 2026, 02:10 UTC1.00under a minute
@hiiiaah/574465 Aug 2026, 05:08 UTC@uilal/120317 · this entry6 Aug 2026, 04:59 UTC1.0024 hours
@hiiiaah/575587 Aug 2026, 10:27 UTC@uilal/120431 · this entry7 Aug 2026, 10:27 UTC1.00under a minute
@uilal/120432 · this entry7 Aug 2026, 10:28 UTC@hiiiaah/575597 Aug 2026, 10:28 UTC1.00under a minute
@hiaha/732686 Aug 2026, 02:10 UTC@uilal/120307 · this entry6 Aug 2026, 02:10 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@hiiiaah6 (6/6 hand-verifiable sample passed)1.00under a minute@hiiiaah (42)
@hiaha6 (6/6 hand-verifiable sample passed)1.00under a minute@hiaha (51)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 6 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @hiiiaah. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 8 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,5072,5322,519.56 August 2026 — 2,519 subscribers6 August 2026 — 2,519 subscribers9 August 2026 — 2,524 subscribers12 August 2026 — 2,528 subscribers16 August 2026 — 2,532 subscribers22 August 2026 — 2,526 subscribers25 August 2026 — 2,527 subscribers31 August 2026 — 2,524 subscribers4 September 2026 — 2,522 subscribers8 September 2026 — 2,509 subscribers12 September 2026 — 2,507 subscribers16 September 2026 — 2,508 subscribers2,5086 August 202616 September 2026
12 measurements spanning 42 days, net -11. 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 2,503–2,536 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 18:202,508+1
12 Sept 2026, 19:582,507-2
8 Sept 2026, 22:012,509-13
4 Sept 2026, 00:202,522-2
31 Aug 2026, 21:242,524-3
25 Aug 2026, 15:382,527+1
22 Aug 2026, 13:562,526-6
16 Aug 2026, 02:142,532+4
12 Aug 2026, 07:142,528+4
9 Aug 2026, 14:152,524+5
6 Aug 2026, 05:332,519no change
6 Aug 2026, 02:192,519first reading

Engagement

40 posts held, back to 6 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 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 40 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

50 reactions across 20 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
50100.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 20 of the 40 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 50 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 6 August 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, 16:00 UTC11 views2 reactionsread 7 August 2026

لا حول ولا قوة الا بالله

2

7 Aug 2026, 16:00 UTC11 views2 reactionsread 7 August 2026

اللهم صل وسلم على نبينا محمد

2

7 Aug 2026, 15:03 UTC15 views3 reactionsread 7 August 2026

لا حول ولا قوة الا بالله

3

7 Aug 2026, 15:03 UTC15 views3 reactionsread 7 August 2026

اللهم صل وسلم على نبينا محمد

3

7 Aug 2026, 14:04 UTC21 views3 reactionsread 7 August 2026

لا حول ولا قوة الا بالله

3

7 Aug 2026, 14:04 UTC21 views3 reactionsread 7 August 2026

اللهم صل وسلم على نبينا محمد

3

7 Aug 2026, 13:55 UTC23 views2 reactionsread 7 August 2026

اللهم بلغني أهدافي وأحلامي اللهم بلغني مبتغاي وأفرح قلبي بمناي وحقق لي مرادي وطموحي بيسر وعافية

2

7 Aug 2026, 13:34 UTC28 views3 reactionsread 7 August 2026

ادعية لـ ساعة الاستجابة ❤️

3

7 Aug 2026, 13:07 UTC30 views3 reactionsread 7 August 2026

لاتنسوني من دعواتكم ولكم بالمثل ❤️

3

7 Aug 2026, 13:07 UTC30 views4 reactionsread 7 August 2026

‏يااااارب الوظيفة الزينه من حيث لا أحتسب.

4

7 Aug 2026, 13:03 UTC27 views3 reactionsread 7 August 2026

لا حول ولا قوة الا بالله

3

7 Aug 2026, 13:03 UTC30 views3 reactionsread 7 August 2026

اللهم صل وسلم على نبينا محمد

3

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

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.

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.

أنت قدها 🩶.
@nta2d · 43,740
Telegram ranks this channel #34 of 84 here — alongside 83 others — read 30 August 2026

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

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

“تذكير بـ الحوقلة و صلاه ع النبي” (@uilal), 2,508 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/uilal.

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.