Telegram RegisterThe public register of Telegram
Telegram profile photo for ⤶صُـحـ𓂆ـبـة'.

Channel

⤶صُـحـ𓂆ـبـة'.

@mnbvcxzhnkd

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

11,538subscribers

+4,618 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001914957325
TypeChannel
Username@mnbvcxzhnkd
Description⤶ " وإن ضاقت بك الأركانُ يومًا، فَرُكن الله رحبٌ لا يضيقُ.🤎 " خذ ما شئـت فأنهـا لله
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 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/mnbvcxzhnkd

Topic

Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 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
@Mohamedyoussef2/224468 Aug 2026, 18:44 UTC@mnbvcxzhnkd/13968 · this entry8 Aug 2026, 18:48 UTC1.004 minutes
@Mohamedyoussef2/224579 Aug 2026, 18:55 UTC@mnbvcxzhnkd/13984 · this entry9 Aug 2026, 20:08 UTC1.0073 minutes
@Mohamedyoussef2/2248911 Aug 2026, 09:46 UTC@mnbvcxzhnkd/14024 · this entry11 Aug 2026, 10:05 UTC1.0019 minutes
@Mohamedyoussef2/231992 Nov 2026, 06:32 UTC@mnbvcxzhnkd/15080 · this entry2 Nov 2026, 06:56 UTC1.0024 minutes
@Mohamedyoussef2/232184 Nov 2026, 10:09 UTC@mnbvcxzhnkd/15112 · this entry4 Nov 2026, 10:28 UTC1.0019 minutes
@Mohamedyoussef2/2338514 Nov 2026, 14:28 UTC@mnbvcxzhnkd/15241 · this entry14 Nov 2026, 21:49 UTC1.007.3 hours
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
@Mohamedyoussef214 (8/8 hand-verifiable sample passed)1.0049 minutes@Mohamedyoussef2 (14–0)
@walhqni_belsalhine13 (8/8 hand-verifiable sample passed)1.0063 minutes@walhqni_belsalhine (12–1)

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. 26 of the 26 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 126 comparable posts for this entry, running 6 August 2026 to 16 November 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).

Recorded under the key clone_copy, last confirmed 17 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.

Growth

6,91111,5389,224.57 August 2026 — 6,920 subscribers7 August 2026 — 6,920 subscribers8 August 2026 — 6,911 subscribers11 August 2026 — 6,964 subscribers14 August 2026 — 6,992 subscribers17 August 2026 — 7,009 subscribers20 August 2026 — 7,101 subscribers24 August 2026 — 7,313 subscribers26 August 2026 — 7,335 subscribers29 August 2026 — 7,366 subscribers1 September 2026 — 7,407 subscribers5 September 2026 — 7,573 subscribers11 September 2026 — 7,785 subscribers14 September 2026 — 7,874 subscribers19 September 2026 — 8,050 subscribers28 September 2026 — 8,257 subscribers5 October 2026 — 8,632 subscribers12 October 2026 — 9,318 subscribers15 October 2026 — 9,604 subscribers17 October 2026 — 9,834 subscribers21 October 2026 — 10,043 subscribers22 October 2026 — 10,145 subscribers23 October 2026 — 10,225 subscribers24 October 2026 — 10,308 subscribers25 October 2026 — 10,411 subscribers26 October 2026 — 10,480 subscribers27 October 2026 — 10,524 subscribers28 October 2026 — 10,566 subscribers29 October 2026 — 10,625 subscribers30 October 2026 — 10,676 subscribers31 October 2026 — 10,731 subscribers1 November 2026 — 10,786 subscribers2 November 2026 — 10,851 subscribers4 November 2026 — 10,914 subscribers5 November 2026 — 10,962 subscribers6 November 2026 — 11,024 subscribers7 November 2026 — 11,092 subscribers8 November 2026 — 11,171 subscribers9 November 2026 — 11,227 subscribers11 November 2026 — 11,287 subscribers14 November 2026 — 11,387 subscribers17 November 2026 — 11,538 subscribers7 August 202617 November 2026
42 measurements spanning 102 days, net +4,618. 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 6,217–12,232 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
17 Nov 2026, 13:3511,538+151
14 Nov 2026, 08:4911,387+100
11 Nov 2026, 10:4011,287+60
9 Nov 2026, 13:0111,227+56
8 Nov 2026, 08:0911,171+79
7 Nov 2026, 04:0911,092+68
6 Nov 2026, 02:5611,024+62
5 Nov 2026, 00:3610,962+48
4 Nov 2026, 01:3710,914+63
2 Nov 2026, 22:2810,851+65
1 Nov 2026, 20:4810,786+55
31 Oct 2026, 17:5910,731+55
30 Oct 2026, 19:5610,676+51
29 Oct 2026, 17:3710,625+59
28 Oct 2026, 16:2010,566+42
27 Oct 2026, 16:0010,524+44
26 Oct 2026, 18:4610,480+69
25 Oct 2026, 15:1510,411+103
24 Oct 2026, 16:1010,308+83
23 Oct 2026, 12:3510,225first reading

Engagement

311 posts held, back to 6 August 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 48 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.31%
avg views ÷ 11,538 subscribers
Avg views / post
266
188 posts measured
Reaction rate
4.70%
reactions ÷ views · ER floor
Posts in window
191
of 311 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held311 (6 August 2026 – 17 November 2026)
Views total50,051
Reactions total2,351
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 03:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
702
Videos
314
Links
32

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
6m 43s
Average length
40s

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

3,340 reactions across 303 posts, in 13 distinct kinds. The most used accounts for 52.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,76352.8%
🍓3339.97%
custom 60034314902207239102778.29%
😢1554.64%
🥰1554.64%
🕊1474.40%
😁1404.19%
😭1223.65%
💔832.49%
💘702.10%
🤣601.80%
💯300.898%
🤗50.15%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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 303 of the 311 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 3,340 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 311 most recent posts we hold, published 6 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 18 of 191 posts held from the last 30 days (9.42%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 20:42 UTC62 views8 reactionsread 18 November 2026

قال الإمام ابن رجب رحمه الله-: ‏قيام الليل يُوجب علو الدرجات في ‏الجنّة قال الله تعالى لنبيه: ‏{ومن اللّيلِ فتهَجّدْ به نافِلةً لك عسى ‏أن يبْعَثكَ ربُّك مقامًا محمودا} ‏فجعل جزاءه على التهجد بالقرآن ‏بالليل أن يبعثه لمقام المحمود ‏وهو أعلى درجاته..

❤8

17 Nov 2026, 19:40 UTC89 views8 reactionsread 18 November 2026

‏مهما كانت الدنيا جميلة تبقى ممراً للآخرة وماعند الله خير وأبقى.. أسأل الله أن يرزقنا وإياكم منازل السعداء.

❤7🍓1

17 Nov 2026, 17:47 UTC143 views8 reactionsread 18 November 2026

‏اللّٰهُمَّ اجمع الشتيتين، اجمَع كُلَّ حَبيبٍ بحبيبهِ. ‏يا ربّ يا كريم! ‏حَنِّن ولين قلب المحبوب على مُحبِّه. ‏ولا غيّب اللّٰه وجه حبيبٍ عن حبيبه ‏ولا أذاقَ أحدًا مرارة البُعد بعد حلاوة القرب. ‏واللّٰهُمَّ اجعل لمن ليس له حبيب، حبيب يحبه ويحب الحياةَ من أجلهِ.

❤7🍓1

17 Nov 2026, 17:05 UTC154 views7 reactionsread 18 November 2026

إحذر أن تعُق أمّك من أجل زوجتك وإياك أن تظلم زوجتك من أجل أمّك الأمّ لها حق والزوجة لها حق، فاعطِ كل ذّي حقٍ حقه..

❤6🍓1

17 Nov 2026, 14:40 UTC180 views10 reactionsread 18 November 2026

الــــدنيــا قصيـرة وإن طـالـت صغيـرة وإن ڪبُـرت زائلـة وإن تـزيّنـت فاحـذر أن تغـرق في بحـارهـا

❤9🍓1

17 Nov 2026, 11:20 UTC190 views9 reactionsread 18 November 2026

. الأغَانِي رَديئة يا ناس تُميتَ القَلب تُكسب الذّنبْ هِي سَيّئة جداً لا تجعَلهَا إهدَاء لأحَد فَالّذي يُحِبُّ شَخصاً لا يُهديهِ ذُنوباً جَارِيَة

❤4🕊3🍓2

17 Nov 2026, 09:37 UTC203 views7 reactionsread 18 November 2026

سيئات جارية.. آتمنى مـن ڪࢦ شخص منا مراجعة الصور ومقاطع الفيديو التي يضعها فـي أي حساب له اتقِ اللہ انت تضع صورة أو المقطع وقد لا تنظر إليها إلا مࢪة ولڪن هناڪ مـن ينظر إليها ويـﺳتمع إليها عدة مرآت وڪم مـن شخص نظر إليها وعليك إثم نظرته فاتقوا اللہ وتذڪروا دائما ڪما أن هناڪ حسنات جاريه فهناڪ سيئات جاريه أيضًا..

❤5🍓1😭1

17 Nov 2026, 08:34 UTC186 views10 reactionsread 18 November 2026

صلِّ الضحى واربِط فؤادَك بالذي ‏مَلَـكَ الخـزائـنَ وابتهِـل برجائِـكْ ‏فهـو الشكـورُ إذا قصـدتَ سبيلِـه ‏وهو القديرُ على جوابِ دعائِـــكْ

❤9🍓1

17 Nov 2026, 07:26 UTC180 views9 reactionsread 18 November 2026

السعادة سر لا تعرفه إلا النفوس المتسامحة المتواضعة التي شعارها نحن وليس أنا جالس العلماء بالعقل وجالس الأمراء بالعلم وجالس الأصدقاء بالأدب وجالس أهل بيتك بالعطف وجالس السفهاء بالحلم وكن جليس ربك بالتسبيح وكن جليس نفسك بالمحاسبة فكُلَّ شيءٍ ينقص إذا قسمته على إثنين إلا السعادة فإنها تزيد إذا تقاسمتها مع الآخرين

❤7🍓1🕊1

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

Posts edited after publishing

@mnbvcxzhnkd edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
6 November 2026
Most recent edit
6 November 2026

Posts recorded as deleted after publishing

We recorded 12 posts on @mnbvcxzhnkd as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
17 November 2026
Median time before seen missing
17 hours
Seen missing in the last 30 days
10

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

8 Aug 2026, 07:32 UTCAnonymous Poll29 voters

تحبو اكمل تنزيل التلاوات الي بسجلها

  1. كمل 💯93%
  2. عادي3%
  3. لا3%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 311 most recent posts we hold, published 6 August 2026 to 17 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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

“⤶صُـحـ𓂆ـبـة'.” (@mnbvcxzhnkd), 11,538 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/mnbvcxzhnkd.

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.