Channel
@alshahidmahmoodjabir
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
850subscribers
-79 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002011346012 |
|---|---|
| Type | Channel |
| Username | @alshahidmahmoodjabir |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 October 2026 |
| On Telegram | t.me/alshahidmahmoodjabir |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Oct 2026, 12:56 | 850 | -10 |
| 8 Oct 2026, 06:17 | 860 | -14 |
| 28 Sept 2026, 01:57 | 874 | -11 |
| 14 Sept 2026, 12:37 | 885 | -8 |
| 7 Sept 2026, 10:39 | 893 | -14 |
| 30 Aug 2026, 03:13 | 907 | -7 |
| 23 Aug 2026, 17:14 | 914 | -7 |
| 15 Aug 2026, 11:57 | 921 | -8 |
| 8 Aug 2026, 11:10 | 929 | no change |
| 7 Aug 2026, 11:48 | 929 | first reading |
20 posts held, back to 27 September 2024 — 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 10 November 2025. An engagement rate over an empty window would be a number about nothing.
415 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 62.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 259 | 62.4% | |
| 💔 | 92 | 22.2% | |
| 😢 | 35 | 8.43% | |
| 🫡 | 16 | 3.86% | |
| 🕊 | 12 | 2.89% | |
| 🙏 | 1 | 0.241% |
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 18 of the 20 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 415 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 September 2024 to 10 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
﴿أَمْ مَنْ هُوَ قَانِتٌ آنَاءَ اللَّيْلِ سَاجِدًا وَقَائِمًا يَحْذَرُ الْآخِرَةَ وَيَرْجُو رَحْمَةَ رَبِّهِ قُلْ هَلْ يَسْتَوِي الَّذِينَ يَعْلَمُونَ وَالَّذِينَ لَا يَعْلَمُونَ إِنَّمَا يَتَذَكَّرُ أُولُو الْأَلْبَابِ﴾ - قِيامُ اللَّيلِ 🤍.
❤6🕊1
﴿أَمْ مَنْ هُوَ قَانِتٌ آنَاءَ اللَّيْلِ سَاجِدًا وَقَائِمًا يَحْذَرُ الْآخِرَةَ وَيَرْجُو رَحْمَةَ رَبِّهِ قُلْ هَلْ يَسْتَوِي الَّذِينَ يَعْلَمُونَ وَالَّذِينَ لَا يَعْلَمُونَ إِنَّمَا يَتَذَكَّرُ أُولُو الْأَلْبَابِ﴾ - قِيامُ اللَّيلِ 🤍.
❤8
عَن روحِ قَمَرِنا 🤍.
🫡12❤3
أَتَىٰ العِيدُ دَونَكُم، للهِ دَرّ قُلوبنا المَكلومَةِ! تَقَبَّلَ اللهُ جِهادَكُما وَشَبابكما يَا خَير الإخوَة 🖤.
💔13❤3🕊2
عَن روحِ قَمَرِنا 🤍.
❤19
مَاريو، البَزَّم وَالعُمدَة - تَقَبَّلَهُم اللهُ - 🖤🖤.
❤22😢7
نحن لا ننسى الشهداء.. ذكرى إرتقاء ثلة من أقمار طولكرم الشهيد المجاهد: محمود سامر جابر الشهيد المجاهد: غيث ياسر شحادة الشهيد المجاهد: جهاد حاتم عمارنة الشهيد المجاهد: أسعد فتحي زهرة الشهيد المجاهد: وليد عبد الرازق زهرة سرايا القدس _كتيبة طولكرم
❤13🕊2😢2
أُمَّاه! أَنَا لَستُ بَعيدَاً.. فَسَلِي قَلبَكِ إِنِّي فِيه 🖤🖤.
❤22
قَبل عَامٍ فِي مِثلِ هَـٰذَا اليَوم تَلَقَّينَا خَبَر فقدكَ يَا بَزَّم وَارتحالك عَنَّا، لَن نُخفيكَ سِرَّاً فَواللهِ لَم تَذهَب ذِكراكَ عَنَّا طِوال هـٰذِهِ الأَيَّام وَاللَّحَظات.. مَا أَسرَعَ الأَيَّام وَما أَبطَأَها فِي حَضرَتِكَ شَهيدنا! مَا أَقسَىٰ أَيّامنا دُونك وَدونَ الرِّفاق، لَو تَعلَم مَا حَصَلَ بَعدَمَا غِبتَ عَن هـٰذِهِ البِلادِ، قَد بَاتَت بَعدك بِلَا رُوحٍ ! نَم وَاهنَأ بِمَا خَصَّكَ الرَّحمـٰن لَه…
❤14💔7
اِقتَرَبَت ذِكرَىٰ رَحيلك عَنَّا يَا سَيِّد الذِّكرَىٰ! يَومانِ عَلَىٰ اِكتمالِ العَامِ وَأَنتَ غائِبُ الجَسَدِ عَنَّا حَاضِر الرُّوح يَا سَيِّدَ القُلوبِ كُلّها 🖤🖤.
💔14❤1
Showing the 12 most recent of 20 posts we hold for @alshahidmahmoodjabir. 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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 15 October 2026 — this entry's latest reading, not the date you are reading this.
“الشَّهيد مَحمود جابِر (البَزّم)” (@alshahidmahmoodjabir), 850 subscribers as measured 15 October 2026. Telegram Register, tgregister.com/channel/alshahidmahmoodjabir.
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.