Channel
@mokhayam_tulkarem
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
3,185subscribers
-215 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002127124019 |
|---|---|
| Type | Channel |
| Username | @mokhayam_tulkarem |
| 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 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/mokhayam_tulkarem |
International news — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 Sept 2026, 14:38 | 3,185 | -10 |
| 12 Sept 2026, 09:38 | 3,195 | -16 |
| 8 Sept 2026, 05:37 | 3,211 | -31 |
| 3 Sept 2026, 10:57 | 3,242 | -19 |
| 30 Aug 2026, 19:28 | 3,261 | -23 |
| 27 Aug 2026, 15:02 | 3,284 | -22 |
| 24 Aug 2026, 07:43 | 3,306 | -19 |
| 20 Aug 2026, 15:35 | 3,325 | -20 |
| 17 Aug 2026, 14:14 | 3,345 | -20 |
| 14 Aug 2026, 14:14 | 3,365 | -15 |
| 11 Aug 2026, 02:02 | 3,380 | -19 |
| 7 Aug 2026, 16:16 | 3,399 | -1 |
| 7 Aug 2026, 13:30 | 3,400 | no change |
| 7 Aug 2026, 12:52 | 3,400 | first reading |
20 posts held, back to 10 January 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 2 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 20 posts for this entry, the most recent from 11 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
33 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 42.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 42.4% | |
| 💔 | 14 | 42.4% | |
| 😢 | 5 | 15.2% |
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 7 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 33 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 10 January 2026 to 11 January 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.
ارتفاع الوفيات بسبب البرد إلى 21 .. المكتب الإعلامي الحكومي بغزة يحمّل الاحتلال الإسرائيلي المسؤولية الكاملة والمباشرة عن الوفيات بسبب البرد في ظل افتقار مخيمات النزوح لمقومات الحياة ووسائل التدفئة...
💔8❤4😢1
طائرات مروحية إسرائيلية تطلق النار جنوب شرقي مدينة خان يونس جنوبي قطاع غزة... .
❤2
لمن يهمه الأمر : سيضرب غزة منخفض جوي هو الأعنف والأشد بعد غدٍ الإثنين، بحسب الأرصاد. تحدّثوا عنهم قبل أن يقتلهم البرد والصمت💔💔
💔4❤2
عاجل| قصف جوي من طيران الاحتلال على مرتفعات جبل الريحان قضاء جزين جنوب لبنان...
المنخفض الأبرد هذا الموسم يضرب فلسطين… وغزة بلا مأوى ولا حماية منخفض جوي قطبي شديد البرودة يبدأ مساء الاثنين، بأمطار غزيرة ورياح قوية وزخات برد، مع انخفاض حاد على درجات الحرارة قد يصل إلى درجتين في المناطق الجبلية، وتحذيرات من السيول وتدني الرؤية. يأتي هذا المنخفض في وقت يمر فيه قطاع غزة بحالة إنسانية شديدة القسوة، حيث تعيش آلاف العائلات في خيام مهترئة وعلى أنقاض منازلها المدمرة، من دون وسائل تدفئة أو بنية تصريف تح…
عاجل هيئة الأسرى ونادي الأسير: استشهاد المعتقل حمزة عبد الله عدوان (67 عامًا) من غزة داخل سجون الاحتلال، بعد اعتقاله رغم معاناته من أمراض مزمنة، في ظل استمرار جرائم التعذيب والإهمال الطبي بحق الأسرى...
قريباً قريباً غضب اللّٰه قادمٌ لا مَحالة سَيدفعُ كُلّ من خَذَل وحـ...ـارب غـ..ـزة الثمن الغضبُ قادم اتقوه فإنه لن يُصيب الذين ظَلموا منكم خاصة... ابراهیم حذیفة الكحلوت
من قال حين يأوي إلى فراشه: لا إله إلا الله وحده لا شريك له، له الملك وله الحمد وهو على كل شيءٍ قدير ، سبحان الله، الحمدلله، لا إله إلا الله، الله أكبر ، لا حول ولا قوة إلا بالله ، غُفرت ذنوبه ولو كانت مثل زبد البحر 🤍🌸
❤3
جيش الاحتلال: رصدت قواتنا اليوم جنوب قطاع غزة ثلاثة غزيين عبروا الخط الأصفر واقتربوا من القوات.. حاول أحدهم سرقة معدات تابعة للجيش ثم لاذ بالفرار، وفور رصده إستهدفته القوات الجوية.. وفي حادثتين إضافيتين في شمال قطاع غزة، رصدت قواتنا عددًا من الغزيين عبروا الخط الأصفر.. فور رصدهم، قتلت القوات غزيين اثنين للقضاء على التهديد...
وفاة الطفل محمد وسام أبو هربيد عمره شهرين في مدينة غزة بسبب البرد الشديد💔...
😢4
نتنياهو: إذا قامت إيران بمهاجمتنا فستكون لذلك عواقب مدمّرة🔥...
أحد معتقلي دعم المقاومة في السجون الأردنية.. المهندس "عبد الله هشام" يواصل إضرابه عن الطعام لليوم السابع؛ للمطالبة بحقوقه المشروعة في الزيارة والعلاج وإدخال الملابس الشتوية...
Showing the 12 most recent of 20 posts we hold for @mokhayam_tulkarem. 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 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 9 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“مخيم طولكرم الآن🖤🔥” (@mokhayam_tulkarem), 3,185 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mokhayam_tulkarem.
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.