💢stay tuned for our next steps https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat https://t.me/jambiya_yemen_leak_chat
❤5👏3🔥3👍2

Channel
@jambiya_yemen
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
279subscribers
-19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002376954615 |
|---|---|
| Type | Channel |
| Username | @jambiya_yemen |
| Created | Between 1 September 2024 and 21 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/jambiya_yemen |
Hacking & security — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 25 Sept 2026, 17:36 | 279 | -6 |
| 12 Sept 2026, 08:15 | 285 | -1 |
| 4 Sept 2026, 14:15 | 286 | -1 |
| 21 Aug 2026, 03:14 | 287 | -3 |
| 14 Aug 2026, 13:28 | 290 | -8 |
| 6 Aug 2026, 22:33 | 298 | no change |
| 6 Aug 2026, 11:08 | 298 | first reading |
20 posts held, back to 21 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 22 October 2024. An engagement rate over an empty window would be a number about nothing.
28 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 39.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 39.3% | |
| ❤ | 7 | 25.0% | |
| 🔥 | 5 | 17.9% | |
| 👏 | 4 | 14.3% | |
| 👎 | 1 | 3.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 8 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 28 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 21 October 2024 to 22 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💢stay tuned for our next steps https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat https://t.me/jambiya_yemen_leak_chat
❤5👏3🔥3👍2
This is our first cyber physical attack to Haifa port. From now on with the obtained data from all partners of Israel via cyber breach to the infrastructures of Haifa port none of them would be safe. All of your data are in our hands. https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat
🔥2
Zim hacked by #jambiya https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat
partner of genocide in Gaza Orian hacked by #jambiya https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat
now partner of genocide in Gaza DSV hacked by #jambiya https://t.me/jambiya_yemen https://t.me/jambiya_yemen_leak Join to group: https://t.me/jambiya_yemen_chat
💢Become a channel member to access important information and documents of Haifa port: https://t.me/jambiya_yemen_leak
👍2👎1
https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
👍3
Partner of genocide in Gaza Port2port hacked by #jambiya https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
One of the actives caused genocide in Gaza allcargo hacked by #jambiya https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
❤2👍2👏1
https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
Partner of genocide in Gaza Allalouf and group207 hacked by #jambiya https://t.me/jambiya_yemen Join to group: https://t.me/jambiya_yemen_chat
👍1
Showing the 12 most recent of 20 posts we hold for @jambiya_yemen. 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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Jambiya” (@jambiya_yemen), 279 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/jambiya_yemen.
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.