Channel
@hebronHAETE
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
6,507subscribers
-1,118 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002178891919 |
|---|---|
| Type | Channel |
| Username | @hebronHAETE |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/hebronHAETE |
National news — 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 60% 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 word for word 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 |
|---|---|---|---|
| @hebronHAETE/67245 · this entry7 Aug 2026, 08:23 UTC | @nabdnablus/1581937 Aug 2026, 08:23 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @nabdnablus | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (7–2) |
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. 1 of the 1 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 7 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.
Across the whole group of 2, the earliest publisher we hold is @hebronHAETE — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 8 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 06:54 | 6,507 | -24 |
| 4 Nov 2026, 13:12 | 6,531 | -15 |
| 1 Nov 2026, 21:59 | 6,546 | -26 |
| 29 Oct 2026, 22:31 | 6,572 | -24 |
| 27 Oct 2026, 02:36 | 6,596 | +21 |
| 23 Oct 2026, 17:26 | 6,575 | -28 |
| 21 Oct 2026, 03:27 | 6,603 | -39 |
| 18 Oct 2026, 05:35 | 6,642 | -37 |
| 15 Oct 2026, 07:10 | 6,679 | -39 |
| 12 Oct 2026, 15:57 | 6,718 | -64 |
| 6 Oct 2026, 01:39 | 6,782 | -100 |
| 28 Sept 2026, 10:42 | 6,882 | -105 |
| 19 Sept 2026, 02:57 | 6,987 | -59 |
| 14 Sept 2026, 19:56 | 7,046 | -86 |
| 11 Sept 2026, 08:21 | 7,132 | -86 |
| 6 Sept 2026, 13:00 | 7,218 | -74 |
| 2 Sept 2026, 12:14 | 7,292 | -51 |
| 30 Aug 2026, 20:33 | 7,343 | -60 |
| 27 Aug 2026, 11:04 | 7,403 | -40 |
| 24 Aug 2026, 03:24 | 7,443 | first reading |
379 posts held, back to 7 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 22 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 1 of 119 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 379 (7 August 2026 – 7 November 2026) |
| Views total | 2,348 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 06:15 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.
Measured directly from 54 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 379 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 379 most recent posts we hold, published 7 August 2026 to 7 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: 8 of 119 posts held from the last 30 days (6.72%) 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).
رئيس الوزراء وزير الخارجية القطري : - لا يمكن ترك المسألة دون حل ولا يمكن أن نتحمل جولة أخرى من التصعيد بالمنطقة - منذ 7 أكتوبر ورغم ما بذلناه من وساطة لم نشهد سوى عدم الاستقرار في المنطقة - منذ وقف إطلاق النار في غزة قتل أكثر من ألف شخص - في #لبنان نرى ما يجري بعد وقف إطلاق النار حيث لا يزال القصف مستمرا - لا يمكن ترك مسألة #إيران دون حل ولا يمكن أن نتحمل جولة أخرى من التصعيد - نؤمن بأن أفضل طريق لنجمع كل الأط…
عاجل | مدفعية الاحتلال تستهدف شمال مخيم البريج وسط القطاع
تبلغ نابغة الزقزوق 7 سنوات، لكن من يراها يظن أنها لم تتجاوز الرابعة أو الخامسة، وقد لاحظت والدتها الفارق المتزايد بين عمر ابنتها وطولها، فتحول القلق إلى رحلة بحث ملحّة عن علاج غير متوافر في غزة. نابغة ليست حالة منفردة؛ ففي إحدى عيادات القطاع، ارتفع عدد الأطفال الذين يراجعون يوميًا بسبب قصر القامة وتعثر النمو من 5 أو 6 حالات قبل الحرب إلى نحو 35 حالة يوميًا، ولا يمثل الرقم إحصاءً شاملًا، لكنه يكشف حجم أزمة تطال مئات …
🚫🟥 ترامب: نحن نتعامل حاليا مع الإيرانيين وسنرى كيف ستسير الأمور ننفذ ضربات محدودة في #إيران لكنها تحقق أهدافها نفرض أعظم حصار في التاريخ العسكري ولا شيء يمر عبر مضيق هرمز دون موافقتنا نتعامل مع #إيران حاليا وهي تريد بشدة التوصل إلى اتفاق
مصادر محلية: قوات الاحتلال تعتقل فلسطيني خلال اقتحامها مخيم عسكر الجديد شرق نابلس.
اللهمّ أنزِل على أهل الخيام دفئًا كالدِّفئ الذي أحسَّه حذيفة بن اليمان رضي اللّه عنه يوم الأحزاب، اللهمّ أرسِل عليهم قوّةً من عندك تثبّت خيامهم، ولُطفًا يُذهِب برد أجسادهم، وطمأنينة تُطفئ خوفَ أطفالهم.
القيادة المركزية الأميركية: مكافآت مالية تصل إلى 20 مليون دولار وإمكانية نقل مكان الإقامة مقابل أي معلومات بخصوص البرنامج النووي الإيراني.
ترمب لمراسل CNN: "نريد الان من كل واحد (في ايران) ان يبقى في داخل منزله. الخارج ليس امناً". ثم قال "لم نبدأ بضربهم بقوة بعد .لم تبدء بعد الموجة الكبيرة. الكبيرة قادمة قريباً جداً ."
هبوط طيران نقل وشحن عسكري أمريكي في قاعدة الحرير بمحافظة أربيل شمالي العراق، قادم من قاعدتي موفق السلطي في الأردن والعديد في قطر.
#عاجل | التليفزيون الإيراني: اعتراض وتدمير طائرة مسيرة من طراز إم كيو-9 تابعة للجيش الأمريكي
وصلت لترامب تقارير عاجلة تقول ان النظام الايراني سيقوم بتجرية نووية في غضون أيام قليلة. .. اجتمع #ترامب اليوم في وقت مبكر جدا بالمقربين منه "روبيو وپيت وزير الدفاع وقادة عسكريين" في قاعة العمليات وادارة الحرب .. لم يكن نائبه جي دي فانس حاضر او منع من الحضور .. الساعات القادمة خطيرة جدا وحاسمة ..
عاجل | مصادر محلية : قوات الاحتلال تقتحم مخيم الأمعري في مدينة رام الله
Showing the 12 most recent of 379 posts we hold for @hebronHAETE. 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 4 registered channels — 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.
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.
@hebronHAETE named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“الخليل و أهلها " هئيتا "” (@hebronHAETE), 6,507 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/hebronHAETE.
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.