Telegram RegisterThe public register of Telegram
Telegram profile photo for موجز الاخبار

Channel

موجز الاخبار

@mujazalakhbar24

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

253subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002669480751
TypeChannel
Username@mujazalakhbar24
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/mujazalakhbar24

Topic

National 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

Growth

252257254.57 August 2026 — 252 subscribers8 August 2026 — 252 subscribers8 August 2026 — 254 subscribers16 August 2026 — 255 subscribers23 August 2026 — 257 subscribers30 August 2026 — 254 subscribers17 September 2026 — 256 subscribers1 October 2026 — 253 subscribers2537 August 20261 October 2026
8 measurements spanning 55 days, net +1. 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 251–258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 12:37253-3
17 Sept 2026, 02:37256+2
30 Aug 2026, 16:09254-3
23 Aug 2026, 13:36257+2
16 Aug 2026, 18:54255+1
8 Aug 2026, 11:23254+2
8 Aug 2026, 09:20252no change
7 Aug 2026, 15:35252first reading

Engagement

20 posts held, back to 5 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 52s
Average length
1m 56s

Measured directly from 2 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1100.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 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 1 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 5 August 2026 to 7 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

7 Aug 2026, 20:37 UTC24 views1 reactionsread 8 August 2026
Video

اليمن : استهدف مواقع ومركبات تابعة للحوثيين/أنصار الله على جبهة مأرب باستخدام طائرات مسيرة وقذائف مدفعية، مما أدى إلى وقوع إصابات متعددة. ِ

🔥1

7 Aug 2026, 15:30 UTC34 viewsread 8 August 2026

انفجار عنيف يهز مدينة المخأ الساحلية غربي تعز في اليمن.

7 Aug 2026, 15:29 UTC34 viewsread 8 August 2026

‏أردوغان: "اتفاقية مكة" مفتوحة لمشاركة جميع الدول الشقيقة الساعية للسلام والاستقرار

7 Aug 2026, 15:29 UTC34 viewsread 8 August 2026

أردوغان: اتفاقية الدفاع المشترك مع باكستان والسعودية تعزز التعاون الأمني والدفاعي وتطوير الصناعات الدفاعية

7 Aug 2026, 12:14 UTC39 viewsread 8 August 2026
Photo

🚫عضو لجنة الأمن القومي في البرلمان الإيراني إبراهيم رضائي: ينبغي للسعوديين أن يدركوا أن اتفاقاً شكلياً مع تركيا وباكستان لن يحقق لهم الأمن، تماماً كما أن سنوات من استغلال الأمريكيين من جانب واحد لم تجلب لهم الأمن. أصلحوا سياساتكم حتى لا تضطروا إلى التوسل للآخرين طلباً للأمن.

7 Aug 2026, 00:05 UTC48 viewsread 8 August 2026

دوي انفجارات في مدينة مأرب غرب اليمن

6 Aug 2026, 20:20 UTC51 viewsread 8 August 2026

مصدر سعودي رفيع يزعم: تقارير استخباراتية عن تنسيق بين فصائل العراق واليمن لضربات على السعودية. المملكة لن تتوانى عن اتخاذ جميع الإجراءات اللازمة للتعامل مع أي عدوان.

6 Aug 2026, 20:12 UTC50 viewsread 8 August 2026

إطلاق صاروخ باليستي يمني نحو هدف معادي.

6 Aug 2026, 20:12 UTC49 viewsread 8 August 2026

مأرب.. الحوثيون يقطعون - قبل قليل- خدمات الاتصالات ( 77 و 73) عن أجزاء واسعة من محافظة مأرب. #اليمن

6 Aug 2026, 14:07 UTC58 viewsread 8 August 2026

🇾🇪⚡- بيان للجيش اليمني بعد نصف ساعة. 5:30

6 Aug 2026, 13:01 UTC58 viewsread 8 August 2026

🇾🇪⚡- هجوم بالطائرات المسيرة يستهدف شمال مريس بالضالع.

6 Aug 2026, 12:40 UTC51 viewsread 8 August 2026

🇾🇪⚡- "رويترز": مقتل ما لا يقل عن 30 من أفراد "القوات اليمنية الموالية للسعودية" في هجمات على معسكرات في محافظتي مأرب وحضرموت في اليمن

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“موجز الاخبار” (@mujazalakhbar24), 253 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/mujazalakhbar24.

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.