Telegram RegisterThe public register of Telegram
Telegram profile photo for أمجاد الشهداء "الإحتياطية"

Channel

أمجاد الشهداء "الإحتياطية"

@AMJAD_SHU1

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4,633subscribers

+1,142 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003480754118
TypeChannel
Username@AMJAD_SHU1
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/AMJAD_SHU1

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 37% 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 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.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@AMJAD_SHU1/1944 · this entry3 Aug 2026, 18:17 UTC@AMJAD_SHU/327913 Aug 2026, 18:17 UTC1.00under a minute
@AMJAD_SHU/328416 Aug 2026, 17:42 UTC@AMJAD_SHU1/1993 · this entry6 Aug 2026, 17:43 UTC1.00under a minute
@AMJAD_SHU1/1994 · this entry6 Aug 2026, 17:50 UTC@AMJAD_SHU/328426 Aug 2026, 17:50 UTC1.00under a minute
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
@AMJAD_SHU25 (8/8 hand-verifiable sample passed)1.00under a minute@AMJAD_SHU (17–8)

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. 3 of the 3 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 28 comparable posts for this entry, running 3 August 2026 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @AMJAD_SHU. 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.

Channels linked by matching posts

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.

Growth

3,4914,6334,0626 August 2026 — 3,491 subscribers6 August 2026 — 3,494 subscribers9 August 2026 — 3,520 subscribers12 August 2026 — 3,540 subscribers16 August 2026 — 3,673 subscribers19 August 2026 — 3,734 subscribers22 August 2026 — 3,763 subscribers25 August 2026 — 3,769 subscribers28 August 2026 — 3,790 subscribers31 August 2026 — 3,820 subscribers4 September 2026 — 3,842 subscribers9 September 2026 — 3,926 subscribers13 September 2026 — 3,955 subscribers18 September 2026 — 4,004 subscribers27 September 2026 — 4,047 subscribers5 October 2026 — 4,110 subscribers12 October 2026 — 4,396 subscribers15 October 2026 — 4,424 subscribers18 October 2026 — 4,458 subscribers21 October 2026 — 4,487 subscribers24 October 2026 — 4,542 subscribers27 October 2026 — 4,547 subscribers2 November 2026 — 4,591 subscribers5 November 2026 — 4,610 subscribers9 November 2026 — 4,618 subscribers13 November 2026 — 4,633 subscribers6 August 202613 November 2026
26 measurements spanning 100 days, net +1,142. 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 3,320–4,804 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
13 Nov 2026, 22:594,633+15
9 Nov 2026, 08:494,618+8
5 Nov 2026, 15:084,610+19
2 Nov 2026, 06:354,591+44
27 Oct 2026, 16:504,547+5
24 Oct 2026, 21:564,542+55
21 Oct 2026, 19:514,487+29
18 Oct 2026, 09:404,458+34
15 Oct 2026, 12:164,424+28
12 Oct 2026, 05:374,396+286
5 Oct 2026, 11:404,110+63
27 Sept 2026, 17:564,047+43
18 Sept 2026, 06:224,004+49
13 Sept 2026, 17:363,955+29
9 Sept 2026, 22:013,926+84
4 Sept 2026, 08:023,842+22
31 Aug 2026, 10:123,820+30
28 Aug 2026, 06:543,790+21
25 Aug 2026, 12:243,769+6
22 Aug 2026, 18:473,763first reading

Engagement

39 posts held, back to 3 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 3 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 39 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
9m 08s
Average length
1m 01s

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

Recent posts

7 Aug 2026, 22:08 UTC88 viewsread 7 August 2026

📌 منقول للاستئناس والاستبشار بالخير، لا للجزم بتأويل الرؤى أو بناء المواقف والأحكام عليها، والله أعلم بما تحمل الأيام. نسأل الله أن يجعلها رؤيا خيرٍ وبشارة.

7 Aug 2026, 22:08 UTC74 viewsread 7 August 2026
Forwarded from @AMJAD_SHU

رأيتُ اللَّيلةَ في منامِي -وأنا قليلُ الرُّؤَى- أنَّ المجرمينَ ينسحبُونَ مِنْ غزَّةَ، فسألتُ النَّاسَ إلى أينَ انسحبُوا، فقالوا: خرجُوا مِنْ كُلِّ غزَّةَ. وأنا جالسٌ في المسجدِ أنتظِرُ الخُطبةَ جاءني أحدُ روَّادِ المسجدِ من المحافظينَ على الصلواتِ وخاصةً الفجرَ، فقالَ لي: رأيتُ اللَّيلةَ أنِّي أَؤُمُّ في المسجدِ وقدْ امتلأَ بمصلينَ مِنْ جنسياتٍ مختلفةٍ، عرفتُهُم منْ ملابسِهِم وهَيْئاتِهِمْ. فقلتُ لعلَّ رُؤيا الانسح…

7 Aug 2026, 22:01 UTC105 viewsread 7 August 2026

منذ فترة قصيرة عبرت القيادة التركية بشكل واضح بأن أمنها القومي يبدأ من بيروت وصولاً لحلب؛ في رسالة واضحة بأن المنطقة تتغير بالفعل وهي جزء أساسي في عملية التغيير من أجل الحفاظ على مصالحها وأمنها القومي.

7 Aug 2026, 21:56 UTC98 viewsread 7 August 2026

يكمن الإختبار الحقيقي لنجاح هذا ( التحالف ) من عدمه في موقفين قادمين؛ هما: - هجوم إسرائيلي مباشر على سوريا لإحداث تغيير كبير في المشهد هناك .. - هجوم إيراني مباشر أو من وكلاءها على الخليج، تجاه ( السعودية أو الكويت أو غيرها) أو تجاه سوريا من جهة العراق .. ربما هذه المواقف أو شيء قريب منها؛ يعطي صورة حقيقة وتقييم لقوة التحالف وصلابته ونجاحه، وآلية الدفاع الجماعي الذي ستتخذه دول بحجم تركيا وباكستان والسعودية، ومدى خ…

7 Aug 2026, 21:48 UTC775 viewsread 7 August 2026

تحليلٌ يستحقّ القراءة بتأنٍّ حتى آخر سطر؛ رؤيةٌ تربط ارتدادات «طوفان الأقصى» بالتحولات المتسارعة في المنطقة وما قد تحمله الأيام القادمة.

7 Aug 2026, 21:46 UTC809 viewsread 7 August 2026

🖊️..زلزال الطوفان والهزات المتتابعة يأتي الإتفاق التركي السعودي الباكستاني؛ ضمن سياق الهزة الاستراتيجية التي أحدثها طوفان الأقصى، بل لا مبالغة حين نقول أنه الذي خلق البيئة الملائمة لأخذ القرار باتجاه الوصول له في ظروف اقليمية ودولية في غاية التعقيد، وهو تعبير جزئي عن وجه المنطقة الجديد الآخذ بالتشكل سريعاً … الأحداث متسارعة؛ وإرتدادات الزلزال الذي أحدثه الطوفان؛ ستستمر، ونعتقد أن أحجار الدومينو الإسرائيلية تحديداً …

7 Aug 2026, 20:42 UTC201 viewsread 7 August 2026
Forwarded from @AMJAD_SHUVideo

#قريبـــاً.. أنشودة الجيش السوري. منصة أمجاد الشهداء - فلسطين https://t.me/AMJAD_SHU

7 Aug 2026, 17:32 UTC371 viewsread 7 August 2026

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

7 Aug 2026, 17:14 UTC350 viewsread 7 August 2026
Forwarded from @AMJAD_SHUVideo

الشهيد القسامي البطل: محمد حسام شهوان مِن رغدِ "الإمارات" إلى بارود "غزة" هكذا يُكتبُ العهد رجلٌ ترك الدنيا ليشتري الفردوس. غادر رغد العيش في الغربة حين نادى المنادي "يا خيل الله اركبي"، فكان المرابط على المعابر شوقاً للثغور. عاد إلى غزة خلال الهدنة الأولى ليصيغ بدمه ملحمة الثبات؛ من دويّ المدفعية إلى إقدام النخبة، ومن طهر الأمني في "وحدة سهم" إلى زئير المعركة في خانيونس. لم يبرح ثغره، ولم يلقِ سلاحه، حتى اصطفاه …

7 Aug 2026, 16:23 UTC318 viewsread 7 August 2026
Forwarded from @AMJAD_SHUVideo

أنشودة موكب العز والفخار. إهداء لروح الشهيدين الأبطال - الشهيد اللواء أبو شروق شهوان وابنه الشهيد المجاهد أبو صلاح شهوان. إنتاج منصة أمجاد الشهداء - فلسطين https://t.me/AMJAD_SHU

7 Aug 2026, 11:54 UTC430 viewsread 7 August 2026
Forwarded from @AMJAD_SHUVideo

#فاصل.. الشهيد القائد خالد منصور "أبو الراغب" إنتاج منصة أمجاد الشهداء - فلسطين https://t.me/AMJAD_SHU

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

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.

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

“أمجاد الشهداء "الإحتياطية"” (@AMJAD_SHU1), 4,633 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/AMJAD_SHU1.

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.