Telegram RegisterThe public register of Telegram

Channel

Gaza Voice

@Gaza_Voice

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

1,214subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002039694067
TypeChannel
Username@Gaza_Voice
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/Gaza_Voice

Topic

International 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 82% 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.

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

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ltpdailyupdates/88224 May 2026, 18:46 UTC@Gaza_Voice/20921 · this entry26 May 2026, 07:58 UTC1.0037 hours
@ltpdailyupdates/8832 Jun 2026, 21:17 UTC@Gaza_Voice/20922 · this entry4 Jun 2026, 09:21 UTC1.0036 hours
@ltpdailyupdates/88818 Jun 2026, 21:55 UTC@Gaza_Voice/20925 · this entry23 Jun 2026, 04:54 UTC1.004 days
@ltpdailyupdates/8901 Jul 2026, 16:50 UTC@Gaza_Voice/20927 · this entry2 Jul 2026, 03:36 UTC1.0011 hours
@ltpdailyupdates/8918 Jul 2026, 15:51 UTC@Gaza_Voice/20928 · this entry8 Jul 2026, 17:06 UTC1.0074 minutes
@ltpdailyupdates/89210 Jul 2026, 15:01 UTC@Gaza_Voice/20929 · this entry11 Jul 2026, 08:51 UTC1.0018 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ltpdailyupdates15 (8/8 hand-verifiable sample passed)1.0036 hours@ltpdailyupdates (150)

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 15 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 20 comparable posts for this entry, running 28 April 2026 to 6 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).

Across the whole group of 2, the earliest publisher we hold is @ltpdailyupdates. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Also posting the same content

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.

Growth

1,2131,2141,213.57 August 2026 — 1,214 subscribers7 August 2026 — 1,214 subscribers8 August 2026 — 1,213 subscribers11 August 2026 — 1,214 subscribers7 August 202611 August 2026
4 measurements spanning 4 days. 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 1,213–1,214 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 07:411,214+1
8 Aug 2026, 05:111,213-1
7 Aug 2026, 23:161,214no change
7 Aug 2026, 13:051,214first reading

Engagement

20 posts held, back to 28 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.48%
avg views ÷ 1,214 subscribers
Avg views / post
103
6 posts measured
Reaction rate
2.62%
reactions ÷ views · ER floor
Posts in window
6
of 20 held

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 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (28 April 20266 August 2026)
Views total618
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:16 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.

Reaction mix

66 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 97.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬6497.0%
💔23.03%

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 19 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 66reactions 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 28 April 2026 to 6 August 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.

Recent posts

6 Aug 2026, 12:20 UTC40 views2 reactionsread 7 August 2026

Days 1022 - 1029 (Saturday - Saturday) - ⚠️ TW ‼️ Recovery teams retrieve remains of 99+ people from the Abu Sharia & Al-Hassayneh families killed by IOF in multiple air strikes on home in Gaza City ⚠️ Abducted female Palestinian reports sexual harassment, harsh interrogations, threats against her family in Israeli prison 🇵🇸 Ceasefire violations: IOF strikes on Gaza City kill 11 people; drone strikes on Al-Mawasi

🤬2

31 Jul 2026, 13:55 UTC86 views1 reactionsread 7 August 2026

🚩Hamas Agrees on Disarmament Draft Hamas and Palestinian factions agreed to a draft agreement controlling weapons of the resistance in Gaza. The draft includes the gradual and phased inventorying and storage of weapons as part of implementing the “Peace Plan”. According to Al Jazeera, a timetable for implementing the process will be prepared within 14 days (with a possibility of extending the deadline). The draft

🤬1

28 Jul 2026, 04:39 UTC113 views3 reactionsread 7 August 2026

*SUMMARY: Settlers Rampage Across West Bank* On Friday, ~45 IOF-backed settlers from Havat Gilad colony stormed town of Tell near Nablus, firing at Palestinians & trying to break into homes. 🔫 In self-defense, Farouq Ramadan seized their rifle & killed a settler. An IOF soldier was killed as IOF killed Farouq & 3 unarmed Palestinians. 🤬 As elections near, Netanyahu vowed to “avenge” the Israeli criminals. IOF expa

🤬3

28 Jul 2026, 04:39 UTC106 views3 reactionsread 7 August 2026

Days 1013-1021 (Thursday - Friday) ❌ IOF issues expulsion orders for Bureij, Maghazi, Nuseirat camp & Deir al-Balah 🚧 IOF advances & pushes “Yellow Line” further 100 meters west into east Deir al-Balah, forcing 100s of families to flee 🏗️ Satellite imagery reveals IOF rapidly built a giant physical barrier (14 miles) through Gaza, solidifying control over 50% of Gaza 🇵🇸 Ceasefire violations: IOF attacks on Gaza C

🤬3

17 Jul 2026, 04:00 UTC151 views4 reactionsread 7 August 2026

Days 1007-1012 (Friday - Wednesday) 🇺🇸 Armed settlers detain US House Rep. Ro Khanna & his convoy in West Bank visit 🚧 IOF systemic shelling & tanks destruction in south Khan Younis + new expulsion lines around Gaza City expand the "Yellow Line" 🇵🇸 Ceasefire violations: IOF strikes on Gaza City kill 11+ people; attack on Deir al-Balah kills 4 members of Abu Qassem family incl. 6 y/o; attacks on Al-Bureij kill 2 pe

🤬4

17 Jul 2026, 04:00 UTC122 viewsread 7 August 2026

Hamas announced it’d end its governing of Gaza after 19 years. Last week, Hamas declared it was ready to transfer civilian governance to the transitional Palestinian technocratic body, the National Committee for the Administration of Gaza (NCAG), under the US-backed “ceasefire” framework + UN Security Council Resolution 2803, which impose the framework for Gaza's “post-war transition.” 🇪🇬 (NCAG members are currentl

11 Jul 2026, 08:51 UTC158 views4 reactionsread 7 August 2026

Days 1005+1006 (Wednesday & Thursday) 🇮🇷 US attacks Iran w/ airstrikes hitting ~90 targets across south Iran, incl. near Bushehr nuclear plant, killing 14 people & injuring 78 others. Iran fired missiles & drones targeting US bases in allied Gulf states & Jordan 💰 Israeli gov approves bill allowing for freezing of additional Palestinian Authority funds 🇵🇸 Ceasefire violations: IOF drone strikes on Khan Younis kill

🤬4

8 Jul 2026, 17:06 UTC144 views4 reactionsread 7 August 2026

Days 998-1004 (Wednesday - Tuesday) 🇵🇸 Ceasefire violations: IOF airstrikes on Gaza City kill 12+ people incl. senior Egyptian Aid Official Mohammed Wahidi & kid; strikes on Khan Younis kill 6+ people; attacks on al-Mawasi kill 3 people 📄 Peace Now report: rate of land seizure in West Bank unprecedented since 1967 🏥 Sodium bicarbonate shortage due to Israel’s aid blockade affects 240 kidney dialysis patients at Al

💔2🤬2

2 Jul 2026, 03:36 UTC151 views4 reactionsread 7 August 2026

Days 991-997 (Wednesday - Tuesday) 🚧 IOF tanks advance “yellow line” towards Al Atatra Junction (Beit Lahia) forcibly displacing ~30 families + airdropped ammunition sets 3 tents ablaze ⚽️ IOF shot & kill 32y/o Saleem Al-Ashqar, goalkeeper of Khan Younis Services Club 🪖 IOF soldier killed in south Lebanon clashes w/ Hezbollah 🇵🇸 Ceasefire violations: IOF airstrike kills 3 people in al-Maghazi; drone strikes on Be

🤬4

26 Jun 2026, 04:02 UTC163 views4 reactionsread 7 August 2026

Days 985-990 (Thursday - Tuesday) 🇺🇸 US Senate passes bill requiring Trump to seek congressional approval before resuming attacks on Iran 🇱🇧 IOF strikes kill 64+ people across south Lebanon incl. Nabatieh, Sohmor & Tyre despite “ceasefire” on Fri 🇵🇸 Ceasefire violations: IOF airstrikes on Gaza City kill 10 people, incl. kid; airstrikes on Khan Younis kill 3 people; airstrike on Bureij kills 2 people; shot & killed

🤬4

23 Jun 2026, 04:54 UTC176 views2 reactionsread 7 August 2026

Days 979-984 (Friday - Wednesday) 🇺🇸🇮🇷 US & Iran electronically signed an agreement to extend their ceasefire for 60 days. Further analysis will be sent soon! 📝 🚧 AJ report: IOF expanded its “territorial zone” by ~24,7105 acres across Gaza, south Lebanon & south Syria 🪖 IOF reports 5 soldiers injured in south Lebanon ⛑️ 35 patients left Gaza through Rafah crossing for medical treatment 🇵🇸 Ceasefire violations: I

🤬2

16 Jun 2026, 12:05 UTC145 views3 reactionsread 7 August 2026

Days 975-978 (Monday - Thursday) 🇵🇸 Ceasefire violations: IOF airstrikes on Gaza kills 4 people, incl. a kid; attacks on Al-Mawasi kill 2 people; airstrike on Nusseirat kills 1 person 🇱🇧 IOF airstrikes on south Lebanon kill 24 people across Zefta, Ain Qana, Nabatieh, Tyre, Tayr Dibba & Siddiqin 🎣 IOF abducted 9 fishermen off the coasts of Gaza City & Deir al-Balah 🇵🇸 19 Palestinians killed, 1 body recovered, 89 i

🤬3

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

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

“Gaza Voice” (@Gaza_Voice), 1,214 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Gaza_Voice.

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.