Channel
@alaskari_news
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
42,676subscribers
-502 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001689369553 |
|---|---|
| Type | Channel |
| Username | @alaskari_news |
| Description | القناة الجديدة لمنصة الإعلام العسكري بعد حذف المنصات السابقة من قبل تطبيق تلغرام. |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/alaskari_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 08:35 | 42,676 | -36 |
| 18 Aug 2026, 10:43 | 42,712 | -26 |
| 17 Aug 2026, 13:39 | 42,738 | -37 |
| 16 Aug 2026, 06:24 | 42,775 | -69 |
| 14 Aug 2026, 17:53 | 42,844 | -69 |
| 13 Aug 2026, 06:25 | 42,913 | -17 |
| 12 Aug 2026, 06:25 | 42,930 | -64 |
| 11 Aug 2026, 05:11 | 42,994 | -32 |
| 10 Aug 2026, 06:55 | 43,026 | -35 |
| 9 Aug 2026, 05:21 | 43,061 | -47 |
| 8 Aug 2026, 03:11 | 43,108 | -52 |
| 6 Aug 2026, 23:48 | 43,160 | -18 |
| 6 Aug 2026, 11:07 | 43,178 | first reading |
19 posts held, back to 9 December 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 30 pagesof 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 19 posts for this entry, the most recent from 2 January 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 20 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
5,153 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 60.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,113 | 60.4% | |
| 👍 | 1,300 | 25.2% | |
| 🔥 | 411 | 7.98% | |
| 😢 | 329 | 6.38% |
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 19 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 5,153reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 9 December 2024 to 2 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
وزارة الدفاع السورية الحسابات الرسمية لوزارة الدفاع على منصات التواصل الاجتماعي: قناتنا على تلجرام: https://t.me/Sy_Defense قناتنا على يوتيوب: https://www.youtube.com/@Sy_Defense منصة إكس: https://x.com/Sy_Defense?t=Z6-i_R7hkg0zzq0m4nxfCg&s=09 منصة فيسبوك: https://www.facebook.com/profile.php?id=61571582632878
👍126❤69🔥16😢2
#العسكري_ميديا #ردع_العدوان تغطية مراسلنا "عبد الرحمن العيسى" للاشتباكات بين إدارة العمليات العسكرية وخلايا ميليشيات الأسد في ريف طرطوس ضمن الحملة التي أطلقتها الإدارة مع وزارة الداخلية لملاحقة فلول الميليشيا تلغرام: https://t.me/alaskari_mediaa فيسبوك: https://www.facebook.com/alaskeri.rade.aleudwan?mibextid=kFxxJD
❤187👍69🔥31😢1
#العسكري_ميديا #ردع_العدوان تغطية مراسلنا "عبد الرحمن العيسى" لانتشار إدارة العمليات العسكرية في ريف طرطوس ضمن الحملة التي أطلقتها مع وزارة الداخلية لملاحقة فلول عصابات الأسد تلغرام: https://t.me/alaskari_mediaa فيسبوك: https://www.facebook.com/alaskeri.rade.aleudwan?mibextid=kFxxJD
🔥135❤60👍45😢2
بلاغ بتخصيص أرقام تواصل للحالات الطارئة في محافظة ريف دمشق. #إدارة_العمليات_العسكرية #ردع_العدوان
❤100👍46
#الإعلام_العسكري وسط هذه الأجواء التي صبر من أجلها السوريون طوال ثلاث عشر عاماً، نستذكر شهداء الثورة عموماً وشهداءنا في الإعلام العسكري الذين ساهموا في هذا النصر بأرواحهم أثناء تغطيتهم لثورة شعبهم ضد الطاغية بجميع المراحل، وخصوصاً بمعركة التحرير. معركة التحرير "ردع العدوان" قدم فيها الإعلام العسكري اثنين من أبطاله، الشهيد البطل "وليد أبو عبدالرحمن" والشهيد البطل "محمد يوسف بيازيد"، بالإضافة لـ 7 إصابات متفرقة غالبه…
❤293😢137👍65🔥3
بلاغ لعناصر نظام الأسد في محافظة ريف دمشق. #إدارة_العمليات_العسكرية #ردع_العدوان
❤102👍31🔥9
بلاغ لعناصر نظام الأسد في محافظة دمشق. #إدارة_العمليات_العسكرية #ردع_العدوان
❤118👍45
بلاغ هام بتخصيص أرقام ومعرفات تواصل لأهلنا في محافظة دمشق في حال حدوث أي طارئ. #إدارة_العمليات_العسكرية #ردع_العدوان
❤102👍48🔥6
بلاغ لعناصر نظام الأسد في محافظة ديرالزور. #إدارة_العمليات_العسكرية #ردع_العدوان
👍87❤33🔥6
بلاغ لعناصر نظام الأسد في محافظة درعا. #إدارة_العمليات_العسكرية #ردع_العدوان
👍93❤38
بلاغ هام بخصوص المسروقات من مبنى إدارة الهجرة والجوازات بدمشق. #إدارة_العمليات_العسكرية #ردع_العدوان
😢137👍81❤43
تعلن إدارة العمليات العسكرية افتتاح مراكز تسوية لعناصر النظام المجرم في محافظة اللاذقية. #إدارة_العمليات_العسكرية #ردع_العدوان
👍142❤40🔥13😢12
Showing the 12 most recent of 19 posts we hold for @alaskari_news. 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.
Citation-graph rank — 1,017,199 of 1,563,849entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 2 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.
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 13 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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“الإعلام العسكري - نيوز” (@alaskari_news), 42,676 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/alaskari_news.
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.