🔴حيتساريم الجوية .. https://t.me/Almustashaar
🔥860❤251🫡186👍131👏36🤣33🤝19💘17

Channel
@Palestine070100
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
34,926subscribers
-178 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001880831737 |
|---|---|
| Type | Channel |
| Username | @Palestine070100 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Palestine070100 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:48 | 34,926 | -27 |
| 13 Aug 2026, 11:27 | 34,953 | -16 |
| 12 Aug 2026, 10:07 | 34,969 | -38 |
| 11 Aug 2026, 07:31 | 35,007 | -15 |
| 10 Aug 2026, 11:01 | 35,022 | -21 |
| 9 Aug 2026, 10:31 | 35,043 | -23 |
| 8 Aug 2026, 13:18 | 35,066 | -38 |
| 7 Aug 2026, 11:00 | 35,104 | no change |
| 7 Aug 2026, 10:57 | 35,104 | first reading |
20 posts held, back to 15 October 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof 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 16 October 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 August 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.
Measured directly from 3 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.
21,529 reactions across 20 posts, in 40 distinct kinds. The most used accounts for 26.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 5,650 | 26.2% | |
| ❤ | 5,526 | 25.7% | |
| 🤣 | 3,676 | 17.1% | |
| 😁 | 1,035 | 4.81% | |
| 👍 | 900 | 4.18% | |
| 😢 | 710 | 3.30% | |
| 👏 | 669 | 3.11% | |
| 💩 | 658 | 3.06% | |
| 🫡 | 554 | 2.57% | |
| 🤮 | 495 | 2.30% | |
| 🤬 | 392 | 1.82% | |
| 💔 | 198 | 0.92% | |
| ❤🔥 | 185 | 0.859% | |
| 🥰 | 157 | 0.729% | |
| 😭 | 130 | 0.604% | |
| 🤪 | 96 | 0.446% | |
| 🤩 | 75 | 0.348% | |
| 🥱 | 64 | 0.297% | |
| 💘 | 43 | 0.2% | |
| 👎 | 36 | 0.167% | |
| 20 further kinds | 280 | 1.30% |
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 20 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 21,529reactions 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 15 October 2023 to 16 October 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔴حيتساريم الجوية .. https://t.me/Almustashaar
🔥860❤251🫡186👍131👏36🤣33🤝19💘17
🔴بئر السبع واشدود .. https://t.me/Almustashaar
🔥656❤149👍102🫡88👏42💘15👎13🥰13
🔴#عاجل رويترز عن الجيش الإسرائيلي: إيران أعطت التوجيهات لحزب الله لتنفيذ هجمات أمس على الحدود اللبنانية الإسرائيلية .. https://t.me/Almustashaar
🔥475❤98👍77👏56🤬29🥰9🤣4😁1
🔴يديعوت أحرونوت: الجيش الإسرائيلي: حتى الآن، أبلغنا عائلات 199 إسرائيليا أن أبناءهم أسرى في غزة .. https://t.me/Almustashaar
❤355👏79❤🔥47🔥46👍34😁24🥰8🤮6
🔴قبل قليل صفارات الإنذار تدوي في تل أبيب وأسدود وعسقلان ووغان يفنه وسديه عوزياهو وشتوليم وبيت شيكما وبات هدار ونيتسان وبراخيا وبيت عزرا .. https://t.me/Almustashaar
🔥348❤48🫡41👍35👌14🤬8👏7
🔴قناة كان العبرية: مسؤول سياسي: ليس هناك وقف لإطلاق النار، ولا إدخال أي نوع من البضائع إلى قطاع غزة .. https://t.me/Almustashaar
🤬341😢74🤮23👍20❤15🔥7😐5😡4
Voice message, posted without a caption
❤379🔥108🫡39👍32👏28😢28💘5🥰5
Voice message, posted without a caption
❤401🔥91🫡35👍32😢26👏20💘5😱5
🔴صافرات الإنذار تدوي في مستوطنة "موديعين" ومواقع أخرى قرب القدس المحتلة .. 🔴صافرات الإنذار تدوي شمال فلسطين المحتلة .. https://t.me/Almustashaar
❤240🔥55👍23👏21🫡12
🔴عمال غزة الي كانوا بالداخل المحتل بلا مأوى في شوارع الضفه برام الله واهلهم تحت الركام في غزة .. معقول؟؟؟؟؟؟؟؟؟؟؟؟؟؟ شباب حدا يفيدني وين صفوا اسا؟ https://t.me/Almustashaar
😢582💔198😭116👍40❤37😡18👎10🖕3
الترجمة: عزيزي شعب (كنادر) إسرائيل! وما زلنا مصدومين بالنبأ المرير لسقوط صديقنا العزيز *الياهو هروش الـ ١٤* 😢 كان إلياهو شرطيًا حازمًا ومحترفًا بكل المقاييس، إلى جانب التواضع والتواضع. لقد كان دائما رمزا ومثالا وقدوة. وترك إلياهو وراءه زوجة و3 أطفال صغار. لن يرونه مرة أخرى. ولكننا هنا لنقدم ظرفًا دافئًا لزوجة إلياهو وعائلته، وهي أيضًا ضابطة شرطة. أنها الآن في حالة حداد على أعزها جميعًا والذي لن يعود إلى المنزل بعد ا…
🤣1,010💩407🤮267🥱61❤48👍39😁36🎉23
مع ٧٠٠٠ صرماية
😁303🤣114🔥40👏32💯31❤20👍16🥱3
Showing the 12 most recent of 20 posts we hold for @Palestine070100. 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“هجمات فلسطينية🇵🇸✊” (@Palestine070100), 34,926 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Palestine070100.
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.