Channel
@magadli
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry
22,619subscribers
+2,534 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001314402837 |
|---|---|
| Type | Channel |
| Username | @magadli |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/magadli |
Politics & activism — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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. 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 |
|---|---|---|---|
| @magadli/18446 · this entry3 Nov 2026, 18:14 UTC | @AhmadDarawsheh/456623 Nov 2026, 18:14 UTC | 1.00 | under a minute |
| @AhmadDarawsheh/458098 Nov 2026, 10:39 UTC | @magadli/18555 · this entry8 Nov 2026, 10:40 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @AhmadDarawsheh | 14 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | this entry (11–3) |
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 165 comparable posts for this entry, running 4 August 2026 to 11 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.
Recorded under the key clone_source, last confirmed 12 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 15:12 | 22,619 | +178 |
| 9 Nov 2026, 22:05 | 22,441 | +5 |
| 8 Nov 2026, 15:08 | 22,436 | +7 |
| 7 Nov 2026, 12:34 | 22,429 | +18 |
| 6 Nov 2026, 11:01 | 22,411 | +36 |
| 5 Nov 2026, 13:39 | 22,375 | +23 |
| 4 Nov 2026, 13:59 | 22,352 | +22 |
| 3 Nov 2026, 11:56 | 22,330 | +8 |
| 2 Nov 2026, 11:45 | 22,322 | +55 |
| 1 Nov 2026, 08:26 | 22,267 | -6 |
| 31 Oct 2026, 06:58 | 22,273 | +12 |
| 30 Oct 2026, 05:40 | 22,261 | +44 |
| 29 Oct 2026, 06:46 | 22,217 | +456 |
| 28 Oct 2026, 01:27 | 21,761 | +903 |
| 26 Oct 2026, 21:45 | 20,858 | +25 |
| 25 Oct 2026, 23:06 | 20,833 | +13 |
| 24 Oct 2026, 21:19 | 20,820 | +15 |
| 23 Oct 2026, 22:55 | 20,805 | -3 |
| 21 Oct 2026, 16:35 | 20,808 | +9 |
| 20 Oct 2026, 12:45 | 20,799 | first reading |
455 posts held, back to 4 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 78 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 215 of 221 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 455 (4 August 2026 – 12 November 2026) |
| Views total | 793,612 |
| Reactions total | 5,786 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 03:19 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 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 20 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.
10,988 reactions across 442 posts, in 6 distinct kinds. The most used accounts for 29.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 3,212 | 29.2% | |
| 👍 | 3,071 | 27.9% | |
| 🤣 | 3,060 | 27.8% | |
| 👎 | 1,019 | 9.27% | |
| 😡 | 453 | 4.12% | |
| 😢 | 173 | 1.57% |
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 442 of the 455 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 10,988 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 455 most recent posts we hold, published 4 August 2026 to 12 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: 5 of 221 posts held from the last 30 days (2.26%) 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).
نشر أوّل| وزير في الليكود حاول إقناع النائب أحمد طيبي أن ترفض المشتركة التصويت لصالح استبدال رئيس الكنيست أمير أوحانا. الوزير من الليكود قال للطيبي: لا تعطوهم حكومة، لأنهم لن يستجيوا لمطالبكم، ويجب الذهاب إلى انتخابات مجددًا. الطيبي ردّ على الليكود: لا نريد انتخابات، نريد إسقاط نتنياهو وبن غفير.
👏32🤣8
نشر لافت بعد قليل
👍10🤣3
النواب العرب ليسوا بحاجة لشهادة من هؤلاء العنصريين وردّ النائب يوسف جبارين في مكانه بشكل حازم
👍50👎1
عنصرية الاستوديوهات: محلّل في القناة 13 ينسحب من الاستوديو احتجاجًا على استضافة رئيس القائمة المشتركة يوسف جبارين ويتهمه بدعم الإرهاب
😡21👏13🤣5
قد يتفهّم البعض "ليونة" تصريحات الأحزاب العربية في هذه الفترة، ولكن أن يتم شرعنة شنّ الحرب على غزة هكذا؟ هذه خطورة بالغة لم يسبق لها مثيل من قبل الأحزاب العربية
👍60😢3👎2👏2
يوآف سيغالوفيتش في مقابلة لراديو 103FM: حكومة التغيير شنّت هجمات على غزة عندما كان منصور عباس جزءًا من الائتلاف الحكومي، وهذا لن يؤثّر على وجود الموحدة في الحكومة
👎34😢3👏1
آيزنكوت ونتنياهو أصدرا بيانًا مشتركًا حول ذلك - هذه أول مرة يصدران فيها بيانًا مشتركًا
😢6👏1
نتنياهو يعلن أنه سيلتقي آيزنكوت بنفسه وبحضور السكرتير العسكري
بعد هذه الرسالة: السكرتير العسكري لنتنياهو سيلتقي آيزنكوت اليوم لإحاطة أمنية
🤣6😡2
بعد سقوطه في الانتخابات: المدعو يوسف حداد يعلن اعتزاله السياسة والانسحاب من حزب "عمخا يسرائيل"
🤣106👍2😢1
باختصار، آيزنكوت يحذّر نتنياهو من شنّ حرب على إيران
👍10🤣6
آيزنكوت برسالة رسمية لنتنياهو: لا تقم بخطوات خطيرة وغير ضرورية، ولا تضع قادة الأجهزة الأمنية أمام معضلة
👏13🤣3👍1
Showing the 12 most recent of 455 posts we hold for @magadli. 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 28 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 5 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 Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“حديث سياسي - محمد مجادلة” (@magadli), 22,619 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/magadli.
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.