Telegram RegisterThe public register of Telegram
Telegram profile photo for ♪♧ماتې هیلۍ ♤💔

Channel

♪♧ماتې هیلۍ ♤💔

@MUSLIM_YARJANAN

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

4,519subscribers

-225 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001973656505
TypeChannel
Username@MUSLIM_YARJANAN
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/MUSLIM_YARJANAN

Topic

Other / unclassifiable — 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 40% 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@MUSLIMYAR_JANAN/70717 Aug 2026, 14:09 UTC@MUSLIM_YARJANAN/11588 · this entry7 Aug 2026, 14:09 UTC1.00under a minute
@Mohib_Darman/51207 Aug 2026, 14:09 UTC@MUSLIM_YARJANAN/11588 · this entry7 Aug 2026, 14:09 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@MUSLIMYAR_JANAN6 (6/6 hand-verifiable sample passed)1.0011 minuteseven
@Mohib_Darman6 (5/6 hand-verifiable sample passed)1.003.6 hourseven

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. 2 of the 2 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 12 comparable posts for this entry, running 1 July 2025 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 @Mohib_Darman. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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 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

4,5194,7444,631.57 August 2026 — 4,744 subscribers8 August 2026 — 4,744 subscribers11 August 2026 — 4,711 subscribers14 August 2026 — 4,689 subscribers17 August 2026 — 4,648 subscribers20 August 2026 — 4,627 subscribers24 August 2026 — 4,602 subscribers27 August 2026 — 4,584 subscribers29 August 2026 — 4,577 subscribers1 September 2026 — 4,573 subscribers5 September 2026 — 4,546 subscribers10 September 2026 — 4,520 subscribers13 September 2026 — 4,523 subscribers17 September 2026 — 4,519 subscribers7 August 202617 September 2026
14 measurements spanning 41 days, net -225. 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,485–4,778 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 16:184,519-4
13 Sept 2026, 16:184,523+3
10 Sept 2026, 07:174,520-26
5 Sept 2026, 11:184,546-27
1 Sept 2026, 13:474,573-4
29 Aug 2026, 22:244,577-7
27 Aug 2026, 08:474,584-18
24 Aug 2026, 18:484,602-25
20 Aug 2026, 19:024,627-21
17 Aug 2026, 19:084,648-41
14 Aug 2026, 07:454,689-22
11 Aug 2026, 08:024,711-33
8 Aug 2026, 00:044,744no change
7 Aug 2026, 18:334,744first reading

Engagement

24 posts held, back to 1 July 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 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 24 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 38s
Average length
22s

Measured directly from 10 videos 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.

Reaction mix

4 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
250.0%
❤‍🔥125.0%
💔125.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 5 of the 24 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 1 July 2025 to 10 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

10 Aug 2026, 13:50 UTC6 viewsread 12 August 2026
Photo

تر ټولو لوی لیست کی ګډون وکړی 👇👇 @Sayidjan7 دلته هم راسره ملګري شي 👇👇 https://t.me/almadinah30 🖇 https://t.me/abawynat131 ✅️ https://t.me/mnsor145 مونږ وڅاري 👇👇👇👇👇👇 https://t.me/NesarAhmad330 👇👇👇👇👇 https://t.me/ontsag 🖇🖇 https://t.me/bsarisanga30

10 Aug 2026, 13:50 UTC4 viewsread 12 August 2026

https://t.me/nisarahmadsaeed د ګران ورور قاري نثاراحمد سعيد له ترانو خوند واخلي هیله کوم چی چینل درسره فالو کړي ❤️😍 👆👆👆👆👆👆👆

9 Aug 2026, 16:39 UTC6 viewsread 12 August 2026

https://t.me/nisarahmadsaeed د ګران ورور قاري نثاراحمد سعيد له ترانو خوند واخلي هیله کوم چی چینل درسره فالو کړي ❤️😍 👆👆👆👆👆👆👆

9 Aug 2026, 16:39 UTC6 viewsread 12 August 2026
Photo

تر ټولو لوی لیست کی ګډون وکړی 👇👇 @Sayidjan7 دلته هم راسره ملګري شي 👇👇 https://t.me/almadinah30 🖇 https://t.me/abawynat131 ✅️ https://t.me/mnsor145 مونږ وڅاري 👇👇👇👇👇👇 https://t.me/NesarAhmad330 👇👇👇👇👇 https://t.me/ontsag 🖇🖇 https://t.me/bsarisanga30

7 Aug 2026, 14:09 UTC25 viewsread 12 August 2026
Photo

تر ټولو لوی لیست کی ګډون وکړی 👇👇 @Sayidjan7 دلته هم راسره ملګري شي 👇👇 https://t.me/almadinah30 🖇 https://t.me/abawynat131 ✅️ https://t.me/mnsor145 مونږ وڅاري 👇👇👇👇👇👇 https://t.me/NesarAhmad330 👇👇👇👇👇 https://t.me/ontsag 🖇🖇 https://t.me/bsarisanga30

29 Jul 2026, 18:55 UTC38 views1 reactionsread 12 August 2026
Photo

دَ ښار تر غوغا ..! دَ صحرا خاموشي ښه ده ، نه خلڪ ، نه ګیله..! ❤️‍🩹🙂🫴🏻 #ماتي_هیلي

1

10 Nov 2025, 20:30 UTC81 views1 reactionsread 12 August 2026
Forwarded from @MUSLIMYAR_JANANVideo

نـــــوی آیډیټـــــ🫀 ┄┅✵❁••🌼🥰🦋••❁✵┅┄ "ستاسو مینه زموږ خوشحالی " ┄┅✵❁••🌼⃟🥰🦋••❁✵┅┄ ترنم 》مولوی نصرت الله نصرت ایډیټ 》احسان مل ارمان ‏‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌ 🩵 ❍ㅤ ⎙ㅤ ⌲ ╭─┅═💞═┅─╮ 🎬 #احسان مل ارمان💖 ╰─┅═💞═┅─╯

❤‍🔥1

10 Nov 2025, 19:04 UTC62 views1 reactionsread 12 August 2026
Forwarded from @MUSLIMYAR_JANAN

@EHSANMAL9 ده نوم جوړولولپاره ..!

1

10 Nov 2025, 18:44 UTC56 views1 reactionsread 12 August 2026
Forwarded from @MUSLIMYAR_JANANVideo

نـــــوی آیډیټـــــ🫀 ┄┅✵❁••🌼🥰🦋••❁✵┅┄ "ستاسو مینه زموږ خوشحالی " ┄┅✵❁••🌼⃟🥰🦋••❁✵┅┄ ترنم 》سیدمنصورآغاشهاب ایډیټ 》احسان مل ارمان ‏‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌ 🩵 ❍ㅤ ⎙ㅤ ⌲ ╭─┅═💞═┅─╮ 🎬 #احسان مل ارمان💖 ╰─┅═💞═┅─╯

💔1

27 Oct 2025, 13:12 UTC120 viewsread 12 August 2026
Video

یو ځل مو بیا درته نوي آیډیت چمتو کړی دی دخوښي وړ موشه ┄┅✵❁••🌼🥰🦋••❁✵┅┄ "ستاسو مینه زموږ خوشحالی " ┄┅✵❁••🌼⃟🥰🦋••❁✵┅┄ جامونه چا واخیستل تږی ده حرم څوک ول ترنم 》مولوی سید سبحانی اغا شاعࢪ 》شاعر مولوی محمد هاشم ذاکر ایډیټ 》محب درمان ‏‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌ 🩵 ❍ㅤ ⎙ㅤ ⌲ ˡᶦᵏᵉ ᶜᵒᵐᵐᵉⁿᵗ ᶠᵒˡˡᵒʷ ˢʰᵃʳᵉ له داسی نورو ویډیوګانو لپاره دلته راشي خوږو 👇 @Mohib_Darman ╭─┅═

24 Oct 2025, 13:39 UTC≈2,230 views0 reactionsread 12 August 2026
Video

یو ځل مو بیا درته نوي آیډیت چمتو کړی دی دخوښي وړ موشه ┄┅✵❁••🌼🥰🦋••❁✵┅┄ "ستاسو مینه زموږ خوشحالی " ┄┅✵❁••🌼⃟🥰🦋••❁✵┅┄ هغه چاته دوهم وار رجوع مکوه غږ 》مولوی عنایت الله علمی صیب 》 ایډیټ 》محب درمان ‏‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌‌ 🩵 ❍ㅤ ⎙ㅤ ⌲ ˡᶦᵏᵉ ᶜᵒᵐᵐᵉⁿᵗ ᶠᵒˡˡᵒʷ ˢʰᵃʳᵉ له داسی نورو ویډیوګانو لپاره دلته راشي خوږو 👇 @Mohib_Darman ╭─┅═M💞M═┅─╮

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

Named by 1 registered channel — 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“♪♧ماتې هیلۍ ♤💔” (@MUSLIM_YARJANAN), 4,519 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/MUSLIM_YARJANAN.

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.