الكهف | اسبوعيًا كل جمعة بنقرأ سورة الكهف سويًا (اسبوع رقم 4)
👌1
Signed B

Channel
@iihmr0
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
6,430subscribers
+461 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001561481401 |
|---|---|
| Type | Channel |
| Username | @iihmr0 |
| Description | قناة تهتم بنشر كل مايفيد الطلبة ونهدف إلى رفع الحصيلة التعليمية لدى الطلبة مخصصة للتخصصات الهندسية والصحية والحاسوبية |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/iihmr0 |
Local community — 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 51% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ENG_qu/4587 Jul 2026, 01:58 UTC | @iihmr0/3628 · this entry7 Jul 2026, 01:58 UTC | 1.00 | under a minute |
| @ENG_qu/4597 Jul 2026, 12:10 UTC | @iihmr0/3629 · this entry7 Jul 2026, 12:10 UTC | 1.00 | under a minute |
| @iihmr0/3632 · this entry9 Jul 2026, 21:33 UTC | @ENG_qu/4609 Jul 2026, 21:33 UTC | 1.00 | under a minute |
| @iihmr0/3639 · this entry22 Jul 2026, 22:23 UTC | @ENG_qu/46522 Jul 2026, 22:28 UTC | 1.00 | 4 minutes |
| @iihmr0/3640 · this entry22 Jul 2026, 22:27 UTC | @ENG_qu/46622 Jul 2026, 22:28 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ENG_qu | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (3–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 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 24 comparable posts for this entry, running 22 June 2026 to 3 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @ENG_qu. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 18:21 | 6,430 | -7 |
| 6 Nov 2026, 18:36 | 6,437 | +1 |
| 3 Nov 2026, 17:07 | 6,436 | +3 |
| 31 Oct 2026, 20:11 | 6,433 | +3 |
| 28 Oct 2026, 18:59 | 6,430 | +28 |
| 25 Oct 2026, 16:11 | 6,402 | -4 |
| 19 Oct 2026, 06:45 | 6,406 | -14 |
| 15 Oct 2026, 21:26 | 6,420 | +7 |
| 13 Oct 2026, 05:46 | 6,413 | +14 |
| 6 Oct 2026, 17:19 | 6,399 | +13 |
| 30 Sept 2026, 03:21 | 6,386 | +50 |
| 16 Sept 2026, 00:18 | 6,336 | +17 |
| 12 Sept 2026, 02:21 | 6,319 | +9 |
| 8 Sept 2026, 01:39 | 6,310 | +53 |
| 2 Sept 2026, 16:37 | 6,257 | +58 |
| 30 Aug 2026, 05:44 | 6,199 | +3 |
| 27 Aug 2026, 04:06 | 6,196 | +11 |
| 24 Aug 2026, 03:56 | 6,185 | +38 |
| 20 Aug 2026, 08:07 | 6,147 | +30 |
| 17 Aug 2026, 15:07 | 6,117 | first reading |
56 posts held, back to 21 June 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 16 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 21 of 24 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 56 (21 June 2026 – 13 November 2026) |
| Views total | 18,176 |
| Reactions total | 187 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 17:39 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.
Lifetime counters from Telegram’s own channel header, read 14 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.
382 reactions across 46 posts, in 17 distinct kinds. The most used accounts for 55.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 211 | 55.2% | |
| ❤🔥 | 29 | 7.59% | |
| 🔥 | 21 | 5.50% | |
| 😢 | 20 | 5.24% | |
| 😭 | 17 | 4.45% | |
| 👍 | 16 | 4.19% | |
| 🫡 | 15 | 3.93% | |
| 💘 | 12 | 3.14% | |
| 💯 | 11 | 2.88% | |
| 💔 | 7 | 1.83% | |
| 🙏 | 6 | 1.57% | |
| 🏆 | 4 | 1.05% | |
| 😍 | 4 | 1.05% | |
| 🎉 | 3 | 0.785% | |
| 👏 | 3 | 0.785% | |
| 🤩 | 2 | 0.524% | |
| 👌 | 1 | 0.262% |
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 50 of the 56 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 382 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 56 most recent posts we hold, published 21 June 2026 to 13 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.
Telegram’s own ‘edited’ marker: 3 of 24 posts held from the last 30 days (12.5%) 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).
الكهف | اسبوعيًا كل جمعة بنقرأ سورة الكهف سويًا (اسبوع رقم 4)
👌1
Signed B
للمهتمين في المناصب القيادية والمهارات العالمية الأدارية يسرّنا دعوتكم لحضور لقاء بعنوان: "القيادة الأستراتيجية والحوكمة المؤسسية في عصر الذكاء الاصطناعي " بالتعاون مع نادي IEEE الفرع الطلابي بجامعة القصيم 🎙️ ضيف اللقاء: الأستاذ م.سعد الغيداني رئيس استراتيجية شركة Oracle في المملكة العربية السعودية. نبذة عن اللقاء: لقاء معرفي نسلط فيه الضوء على مفاهيم القيادة الاستراتيجية والحوكمة المؤسسية، وأثرهما في نجاح المؤس…
❤1🔥1
Signed B
على طاري المذاكرة نذكركم انه عندنا قناة خاصة بتطبيق Forest غابة مستديم ماسكتها مشرفتنا @eorits حياكم https://t.me/mustadymforest
Signed سكون ✨
السلام عليكم ورحمة الله وبركاته، ١٠ دقايق تفصلنا على بداية لقائنا، حياكم الله. 🔗 رابط حضور اللقاء: https://meet.google.com/mrd-azoh-xcf?hs=224
❤2
Signed Hatem #ECE
فماااااحاااااجة
🔥3❤🔥1
Signed سكون ✨
هاتريك هاتريكككك
❤11💘4🔥4❤🔥3
Signed سكون ✨
وحدوا الدعاء بستمر التعليق للخميس 🙏
❤8😢6🙏6💔2
Signed B
استنادًا لتقرير المركز الوطني للأرصاد ونظرًا للتقلبات الجوية بمنطقة القصيم.. تقرر تحويل الدراسة الحضورية يوم غدٍ الأربعاء 1448/6/1هـ، إلى نظام الدراسة عن بعد لجميع طلاب وطالبات #جامعة_القصيم في جميع مقرات الجامعة.
❤7😢1
Signed B
في الجامعة، تعودنا أن لكل مسألة هندسية معطياتها كاملة وحلها في آخر الكتاب، لكن الميدان يعلّمنا كيف نتخذ القرار حين تغيب هذه المعطيات. لذلك نأخذكم في جلسة حية إلى بيئة العمل الحقيقية، عبر أربع تجارب لطلاب خاضوا التدريب الصيفي في Saudi Airlines وParsons وKACST وGE Vernova. لن نكتفي بما واجهوه هناك، بل سنعود خطوة إلى الوراء لنجيب عن الأسئلة الأهم، من خلال قصص تُروى بصراحة عن التحديات والإخفاقات والدروس التي لم تذكرها ا…
❤3
Signed Hatem #ECE
#فعاليات تتوقعون بكرا تعليق؟ 🫣
👍16💯4😢3
Signed سكون ✨
#تحديث_تطبيق_MyQu صار يطلع إشعار التعليق أطلق تحديث 🥰
❤11❤🔥3
Signed سكون ✨
Photo, posted without a caption
❤8🎉3
Showing the 12 most recent of 56 posts we hold for @iihmr0. 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
فيه فكرة ودنا نسوي قناة إعلانات بحيث ينرسل فيها بعض الأشياء المفيدة لكم كطلاب (اجهزة الكترونية، مستلزمات ورقية، حافظات قهوة، ستيكرات ايبادات [شغل مراهقين]، شنط، الخ) يكون عليها عروض ممتازة من نختلف المتاجر (أمازون، نون، بعض متاجر زملاءنا) شرايكم بالفكرة؟
The shares total 118%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
#فعاليات_كأس_العالم مع مين اليوم؟؟؟ 🔥🔥🔥🔥🔥 اكتبولنا توقعاتكم للنتيجة تحت 👇 الي يطلع توقعه صح بعطيه لايك تستاهلون حبايبي كلكم 👍
The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
شرايكم بفعاليات كأس العالم وخاصة المنتخبات العربية دور 16
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 56 most recent posts we hold, published 21 June 2026 to 13 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“مُستديم | جامعة القصيم 🇸🇦🇵🇸” (@iihmr0), 6,430 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/iihmr0.
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.