Telegram RegisterThe public register of Telegram

Channel

🔈 قناة إﻧ̲ﺷ̲ﺂ̲ﺩ̲يے

@ahmadrkbban

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4,973subscribers

-5 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001001695404
TypeChannel
Username@ahmadrkbban
Description🔈 قناة إﻧ̲ﺷ̲ﺂ̲ﺩ̲يے ☀️ مختصه بنشر الاناشيد الاسلاميه العربيه @ahmadkban
Created19 October 2015measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/ahmadrkbban

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 3 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
@Somsn/434612 Dec 2025, 13:13 UTC@ahmadrkbban/33323 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
@Somsn/434712 Dec 2025, 13:13 UTC@ahmadrkbban/33324 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
@Somsn/434812 Dec 2025, 13:13 UTC@ahmadrkbban/33325 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
@Somsn/434912 Dec 2025, 13:13 UTC@ahmadrkbban/33326 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
@Somsn/435012 Dec 2025, 13:13 UTC@ahmadrkbban/33327 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
@Somsn/435112 Dec 2025, 13:13 UTC@ahmadrkbban/33328 · this entry12 Dec 2025, 13:13 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Somsn7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (61)
@arwamasejat6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (60)
@anaqt_fakr6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (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. None of the 2 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 12 comparable posts for this entry, running 10 November 2024 to 12 December 2025. 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 4, the earliest publisher we hold is @arwamasejat. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 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 3 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

4,9734,9784,975.55 August 2026 — 4,978 subscribers6 August 2026 — 4,978 subscribers6 August 2026 — 4,976 subscribers10 August 2026 — 4,973 subscribers5 August 202610 August 2026
4 measurements spanning 4 days, net -5. 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 4,972–4,979 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 03:514,973-3
6 Aug 2026, 22:504,976-2
6 Aug 2026, 03:484,978no change
5 Aug 2026, 21:184,978first reading

Engagement

20 posts held, back to 13 September 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof 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 12 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,290
Videos
372
Links
226

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
59s
Average length
59s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

12 Dec 2025, 13:17 UTC≈1,190 viewsread 12 August 2026
File

➺🌸┊↷ ‌ #قران_مقطع_صوتي #سورة_الكهف 🌺 👤القارئ: #عبدالولي_الاركاني 🔉 ⇣ سورة الكهف ‏ﻟلقراءة : ‏http://goo.gl/y5Ip 🤝 إدعمنا بإعادة توجيه .✨❤️ ⇣ ​• ___⠀⠀ 💗⠀▸ @Somsn

Signed

12 Dec 2025, 13:15 UTC≈1,130 viewsread 12 August 2026

يَارب أمُور مُيسّـــرة وقَلبٌ مُطمئِن✨❤️

Signed

12 Dec 2025, 13:13 UTC≈1,130 viewsread 12 August 2026

➺🌸┊↷ ‌‏⠀ ‏اللّهم في يوم الجمعة ، حولَك وقوتَك الذي لا يغلِبها شيءٌ ، اللّهم رضاك الذي لا نَبغي سِواه ، اللّهم سعادةَ الدنيا والآخِرة ، اللّهم اجعلنا خيراً مما يظنّون ، واستر علينا ما لا يَعلمون ، واغفِر لنا يومَ لا يَنفع مالٌ ولا بنونٌ ، إلّا من أتاكَ بقلبٍ سليمٍ ‏✨❤️ ⇣ ​• ______⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC957 viewsread 12 August 2026

➺🌸┊↷ ‌‏⠀ ‏اللّهم في يومِ الجُمعةِ ، ارحم مَن توسَّدَت أجسادُهم الأكفانَ ، اللّهم اجعل قبورَهم خَيرَ مسكنٍ تغفُو به أعينُهم ، ياربَّ العالَمين ‏✨❤️ ⇣ ​• ______⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC905 viewsread 12 August 2026

➺🌸┊↷ ‌‏⠀ ‏وما الجُمعةُ إلّا عيداً لقلبِك ، رتِّل آياتِ الكهفِ ، صلِّ على النبيِّ ، وابعث دعواتِك إلى ربِّك ، لِـ تأتيَك البشائِرُ بإذنِه ‏✨❤️ ⇣ ​• ______⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC869 viewsread 12 August 2026

➺🌸┊↷ ‌‏⠀ ‏لمن يقرأ .. اللّهم اغفِر ذنوبَهم ، واستُر عيوبَهم ، وشافِ مريضَهم ، وارزق محتاجَهم ، وارحم أمواتَنا وأمواتَهم وأمواتَ المسلمين ، واغفِر لنا ولهم ، وأَسكِنّا ووالدينا وكلَّ عزيزٍ علينا وعليهم فسيحَ جنّاتِك ، ياربَّ العالمين ‏✨❤️ ⇣ ​• ______⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC828 viewsread 12 August 2026
Photo

➺🌸┊↷ ‌‏⠀ ‏الحمدُ للهِ على يومٍ أَقبَل ونحنُ نسمعُ ونُبصِر ، الحمدُ للهِ على شمسٍ أَشرَقت ونحنُ نُؤمِن ونَشكُر ، الحمدُ للهِ على يومٍ أَقبَل ونحنُ لَم نَفقِد أو نُفقَد ، الحمدُ للهِ ربَّ العالمينَ حمداً كثيراً طيّباً ‏✨❤️ ⇣ ​• __________________⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC795 viewsread 12 August 2026
Photo

➺🌸┊↷ ‌‏⠀ ‏اللّهمَ إنّا نسألُك سِتراً جميلاً ، وصبراً جميلاً ، واتساعاً بعد ضيقٍ ، وراحةً بعد شفاءٍ ، وشفاءً مِن كلِّ مرضٍ ، ونجاةً مِن الهَمِّ ، وتيسيراً لكلِّ صعبٍ ‏✨❤️ ⇣ ​• __________________⠀ ⠀ 💗⠀▸

Signed

12 Dec 2025, 13:13 UTC804 viewsread 12 August 2026

➺🌸┊↷ ‌‏⠀ ‏اللهم اجعل القرآن ربيع قلبي. ونور صدري وجلاء حزني وذهاب همي وغمي.‏✨❤️ ⇣ ​• ______⠀ ⠀ 💗⠀▸

Signed

5 Dec 2025, 12:49 UTC879 viewsread 12 August 2026

يَارب أمُور مُيسّـــرة وقَلبٌ مُطمئِن✨❤️

Signed

30 Nov 2025, 12:45 UTC928 viewsread 12 August 2026

يَارب أمُور مُيسّـــرة وقَلبٌ مُطمئِن✨❤️

Signed مــصـﮧـ͜ާـٌطفى ↜

30 Nov 2025, 12:40 UTC903 viewsread 12 August 2026
Forwarded from @Somsn

➺🌸┊↷ ‌‏⠀ ‏لمن يقرأ .. أسألُ اللهَ أن لا يَردَّ لكم دعوةً ، ولا يحرِمَكم فضلَه ، ويحفظَ أهليكُم وأحِبّتَكم ، ويُسعِدَكم ويُفَرِّج هَمَّكم ويُيسِّر أمرَكم ، ويَغفِر لكُم ولوالِديكُم وذريّاتِكم ، وأن يبلِّغَكم أَسمى مراتِبَ الدنيا وأَعلى منازلَ الجنّة ‏✨❤️ ⇣ ​• __⠀ ⠀ 💗⠀▸

Signed مــصـﮧـ͜ާـٌطفى ↜

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“🔈 قناة إﻧ̲ﺷ̲ﺂ̲ﺩ̲يے” (@ahmadrkbban), 4,973 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ahmadrkbban.

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.