Telegram RegisterThe public register of Telegram
Telegram profile photo for 📜عیلمی شەرعی📜

Channel

📜عیلمی شەرعی📜

@ESL4M_M

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Cite this entry

146subscribers

+0 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-1001373005144
TypeChannel
Username@ESL4M_M
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 November 2026
Measurements held11
Confirmed unchanged2 times, most recently 14 November 2026
On Telegramt.me/ESL4M_M

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 25 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 the other topics.

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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@aramy_darun/1491914 Jul 2026, 11:56 UTC@ESL4M_M/1977 · this entry14 Jul 2026, 11:56 UTC1.00under a minute
@ESL4M_M/1978 · this entry15 Jul 2026, 12:26 UTC@aramy_darun/1492015 Jul 2026, 12:26 UTC1.00under a minute
@ESL4M_M/1980 · this entry17 Jul 2026, 11:19 UTC@aramy_darun/1492217 Jul 2026, 11:20 UTC1.00under a minute
@ESL4M_M/1981 · this entry17 Jul 2026, 20:06 UTC@aramy_darun/1492317 Jul 2026, 20:16 UTC1.0010 minutes
@aramy_darun/1492823 Jul 2026, 11:38 UTC@ESL4M_M/1986 · this entry23 Jul 2026, 11:38 UTC1.00under a minute
@ESL4M_M/1987 · this entry23 Jul 2026, 16:59 UTC@aramy_darun/1492923 Jul 2026, 16:59 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@aramy_darun13 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–5)
@uyna_kanm12 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–5)
@regay_b4hasht11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–5)
@tweshyak7 (7/7 hand-verifiable sample passed)1.00under a minute@tweshyak (5–2)

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. None of the 20 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 14 July 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).

Of the group of 6 channels, the one whose matching posts we hold earliest is @regay_b4hasht. That is a statement about our reading window, not a claim of authorship.

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

Channels linked by matching posts

This channel is in a group of 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

145148146.57 August 2026 — 146 subscribers8 August 2026 — 146 subscribers14 August 2026 — 145 subscribers28 August 2026 — 147 subscribers5 September 2026 — 146 subscribers14 September 2026 — 147 subscribers6 October 2026 — 146 subscribers14 October 2026 — 147 subscribers21 October 2026 — 148 subscribers29 October 2026 — 147 subscribers4 November 2026 — 146 subscribers1467 August 20264 November 2026
11 measurements spanning 90 days. 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 145–148 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 15:08146-1
29 Oct 2026, 00:51147-1
21 Oct 2026, 01:46148+1
14 Oct 2026, 03:30147+1
6 Oct 2026, 15:18146-1
14 Sept 2026, 01:20147+1
5 Sept 2026, 23:37146-1
28 Aug 2026, 04:04147+2
14 Aug 2026, 04:06145-1
8 Aug 2026, 21:00146no change
7 Aug 2026, 01:42146first reading

Engagement

20 posts held, back to 14 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 14:18 UTC5 viewsread 8 August 2026

📜مانــای ووشـەکانی قوڕئــــان ✍ووشــەی : ❴ قُرَنَاءَ ❵ ↩واتــە : هاوڕێ و هاووەڵانی خراپ 🔖خوای گەورە دەفەرموێ : ​‏﴿وَقَيَّضْنَا لَهُمْ قُرَنَاءَ فَزَيَّنُوا لَهُم مَّا بَيْنَ أَيْدِيهِمْ وَمَا خَلْفَهُمْ وَحَقَّ عَلَيْهِمُ الْقَوْلُ فِي أُمَمٍ قَدْ خَلَتْ مِن قَبْلِهِم مِّنَ الْجِنِّ وَالْإِنسِ ۖ إِنَّهُمْ كَانُوا خَاسِرِينَ ﴾ 🪵سوڕەتی فصلت ئایەتی :{25}

7 Aug 2026, 08:11 UTC9 viewsread 8 August 2026

📜ئەمڕۆ هەینیە سوڕەتی الکهف بخوێنه 📌پێغەمبەری خوا{ﷺ }فەرمویەتی: ❴ ھەرکەسێك سورەتی الکھف بخوێنێ لەڕۆژی جمعەدا ئەبێتە نورێك بۆی لە نێوان ھەردوو جمعەکەدا ❵ { صحيح الترغيب }

6 Aug 2026, 19:20 UTC11 viewsread 8 August 2026

🪵الله تعالی دەفەرموێ : ❴وَمَا تَدْرِي نَفْسٌ مَّاذَا تَكْسِبُ غَدًا❵ 📌سوڕەتی لقمان ئایەتی (34) نازانی سبەی لەکوێی نازانی سبەی چی دەخۆی نازانی سبەی زیندووی نازانی سبەی کێ دەبینی نازانی سبەی کێ میوانتە نازانی سبەی چی دێتە ڕێگات نازانی سبەی چی ڕوودەدات 📌ئیدی بۆچی خەم بۆ سبەی دەخۆی

31 Jul 2026, 15:52 UTC21 viewsread 8 August 2026

إِنَّ اللَّهَ وَمَلَائِكَتَهُ يُصَلُّونَ عَلَى النَّبِيِّ ۚ يَا أَيُّهَا الَّذِينَ آمَنُوا صَلُّوا عَلَيْهِ وَسَلِّمُوا تَسْلِيمًا

31 Jul 2026, 07:45 UTC21 viewsread 8 August 2026

📜ئەمڕۆ هەینیە سوڕەتی الکهف بخوێنه 📌پێغەمبەری خوا{ﷺ }فەرمویەتی: ❴ ھەرکەسێك سورەتی الکھف بخوێنێ لەڕۆژی جمعەدا ئەبێتە نورێك بۆی لە نێوان ھەردوو جمعەکەدا ❵ { صحيح الترغيب }

29 Jul 2026, 19:03 UTC21 viewsread 8 August 2026

📜مانــای ووشـەکانی قوڕئــــان ✍ووشــەی : ❴ تَلْقَفْ ❵ ↩واتــە : قوتیدەدات یان هەڵیدەلووشێت 🔖خوای گەورە دەفەرموێ : ​‏﴿ وَأَلْقِ مَا فِي يَمِينِكَ تَلْقَفْ مَا صَنَعُوا ۖ إِنَّمَا صَنَعُوا كَيْدُ سَاحِرٍ ۖ وَلَا يُفْلِحُ السَّاحِرُ حَيْثُ أَتَىٰ ﴾ 🗂سوڕەتی طە ئایەتی :{69}

29 Jul 2026, 07:07 UTC18 viewsread 8 August 2026

🧭نوێـژی چێشــتەنگـاو 🧭 🔖پاداشتەکەی 【360】 سەدەقــەیـە ⏰کاتــەکــەی ⏰ 👇👇 📙(20) خولەک سەعاتێک دوای خۆرهەڵات دەست پێ دەکات 📗 (20) خولەک پێش بانگی نیوەڕۆ کۆتایی دێت

25 Jul 2026, 09:05 UTC28 viewsread 8 August 2026

🟫ئایا ئەمانەت زانیووە ؟ 📌هەرکەسێک عارەق (مەی) بخواتەوە بۆ ماوەی چل ڕۆژ پاداشتی نوێژکردنی ئەو چل ڕۆژەی بۆ نانووسرێ بەڵام دەبێ نوێژەکانی بکات بەڵام پاداشتی بۆ نیە 📌هەرکەسێک لەڕۆژی هەینی دوای ئەوەی ئیمام دادەنیشێ بێتە مزگەوتەوە تەنها فەرزی هەینی لەسەر لادەچێت ئەگینا پاداشتی هەینی بۆ نیە 📌خوێندنی سوڕەتی فاتیحە بۆ مردوو ئەسڵ وئەساسی نیە چونکە نە رسول الله (ﷺ) ونە هاوڵان (ڕ.خ) لێبێت نەیانخوێندووە 📌هەرکەسێک لەشیرک بمرێ…

24 Jul 2026, 08:33 UTC24 viewsread 8 August 2026

📜ئەمڕۆ هەینیە سوڕەتی الکهف بخوێنه 📌پێغەمبەری خوا{ﷺ }فەرمویەتی: ❴ ھەرکەسێك سورەتی الکھف بخوێنێ لەڕۆژی جمعەدا ئەبێتە نورێك بۆی لە نێوان ھەردوو جمعەکەدا ❵ { صحيح الترغيب }

23 Jul 2026, 16:59 UTC26 viewsread 8 August 2026

پاداشتی زۆر سەڵاوات دان : خەمـەکــانت نامێــنن تاوانـەکانـت دەسـڕێــنەوە 📜{اللَّهُمَّ صَلِّی عَلَی مُحَمَّدٍ وَّعَلَی آلِ مُحَمَّدِِ }

23 Jul 2026, 11:38 UTC25 viewsread 8 August 2026

🔖خوشکی بەڕێز مەڵێ قەیناکا مادام نوێژ دەکات قەیناکا شووی پێ دەکەم ، نوێژ فەرز و واجبە گومانی تێدا نیە بەڵام ئایا سیمای و ئاکاری دینداری لەو پیاوە هەیە ؟ 📌بۆیە جوان وچاک ورد بەوە لە سیفاتەکانی ئەو پیاوە ئینجا بڕیاری زەواجی لەگەڵ بدە 📜 بۆیـە دوو بەیانی گلەیی لەخراپی پیاوەکەت مەکە چونکە خۆت پەلەت کرد لەهەڵبژاردنی ئەو جۆرە پیاوە

22 Jul 2026, 11:46 UTC21 viewsread 8 August 2026

🟫بەڕاستی کارەساتە 🟫 📌بەداخەوە ئێستا وەرزی هاوینە ئافرەتان دەچنە گەشت و سەیران بەتایبەت لە ناو ڕووبار و ناوچە گەشتیارییەکان ئافرەتان قاچیان هەڵدەکەن لەو ئاوەکە پیاوانیش سەیریان دەکەن بۆیە ئاگادار بن 🪵جا با پیاوان چ برای ئافرەتەکە یان هاوسەری ئافرەتەکە یان باوکی ئافرەتەکە ڕێگە نەدەن بەئافرەتەکانیان وئامۆژگایان بکەن کە ئەو کارە نەکەن

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

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

“📜عیلمی شەرعی📜” (@ESL4M_M), 146 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ESL4M_M.

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.