#عاجل : منتخب #اليمن يحقق نتيجة تاريخية ضد #الكويت https://cratersky.support-f0c.workers.dev/posts/237500 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky

Channel
كريتر سكاي
@cratersky
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
14,852subscribers
-111 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001288526117 |
|---|---|
| Type | Channel |
| Username | @cratersky |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/cratersky |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 13:59 | 14,852 | -7 |
| 2 Sept 2026, 22:23 | 14,859 | -4 |
| 1 Sept 2026, 17:53 | 14,863 | -11 |
| 31 Aug 2026, 20:08 | 14,874 | -11 |
| 30 Aug 2026, 18:34 | 14,885 | -16 |
| 29 Aug 2026, 20:23 | 14,901 | -10 |
| 28 Aug 2026, 19:42 | 14,911 | -6 |
| 27 Aug 2026, 17:33 | 14,917 | +18 |
| 26 Aug 2026, 20:53 | 14,899 | -2 |
| 25 Aug 2026, 21:53 | 14,901 | -2 |
| 24 Aug 2026, 23:02 | 14,903 | -21 |
| 23 Aug 2026, 10:28 | 14,924 | -23 |
| 22 Aug 2026, 00:57 | 14,947 | -5 |
| 20 Aug 2026, 18:45 | 14,952 | +6 |
| 19 Aug 2026, 20:48 | 14,946 | -2 |
| 18 Aug 2026, 22:06 | 14,948 | +1 |
| 17 Aug 2026, 20:06 | 14,947 | -12 |
| 16 Aug 2026, 17:55 | 14,959 | -17 |
| 15 Aug 2026, 00:44 | 14,976 | +9 |
| 13 Aug 2026, 14:06 | 14,967 | first reading |
Engagement
1,048 posts held, back to 6 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 53 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.50%
- avg views ÷ 14,852 subscribers
- Avg views / post
- 669
- 963 posts measured
- Reaction rate
- 0.356%
- reactions ÷ views · ER floor
- Posts in window
- 963
- of 1,048 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 527 of 963 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 1,048 (6 August 2026 – 3 September 2026) |
| Views total | 643,810 |
| Reactions total | 1,402 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 11:13 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.
What this channel posts
- Video runtime
- 27s
- Average length
- 27s
Measured directly from 1 video 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,483 reactions across 523 posts, in 30 distinct kinds. The most used accounts for 37.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 548 | 37.0% | |
| 👍 | 269 | 18.1% | |
| 😁 | 189 | 12.7% | |
| 🤣 | 118 | 7.96% | |
| 💔 | 67 | 4.52% | |
| 🔥 | 44 | 2.97% | |
| 👎 | 39 | 2.63% | |
| 🍌 | 35 | 2.36% | |
| 💩 | 27 | 1.82% | |
| 😡 | 26 | 1.75% | |
| 👏 | 21 | 1.42% | |
| 🖕 | 18 | 1.21% | |
| 🤬 | 18 | 1.21% | |
| 🫡 | 14 | 0.944% | |
| 🥱 | 10 | 0.674% | |
| 🤮 | 9 | 0.607% | |
| 😱 | 6 | 0.405% | |
| 😢 | 5 | 0.337% | |
| 🌚 | 3 | 0.202% | |
| 😭 | 3 | 0.202% | |
| 10 further kinds | 14 | 0.944% |
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 550 of the 1,000 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,483 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 7 August 2026 to 3 September 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
#عاجل | أول شهيد من أبناء #الضالع في جبهة الكدحة بـ #تعز https://cratersky.support-f0c.workers.dev/posts/237499 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
#عاجل : موجة نزوح جديدة من مقبنة والكدحة غربي #تعز https://cratersky.support-f0c.workers.dev/posts/237498 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
❤1
#عاجل : إصابة مسنة بقذيفة هاون حوثية في #الحديدة https://cratersky.support-f0c.workers.dev/posts/237497 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
#عاجل : أسر عنصرين حو ثيين والعثور على 5 جثث في موقع واحد https://cratersky.support-f0c.workers.dev/posts/237496 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
❤1
#عاجل : قصف حو ثي عنيف يستهدف قرى غرب #تعز https://cratersky.support-f0c.workers.dev/posts/237495 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
#عاجل : قوات #طارق_صالح تدفع بتعزيزات عسكرية لإسناد مقاومة #تعز عقب هجوم حو ثي كبير https://cratersky.support-f0c.workers.dev/posts/237494 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
❤1
#عاجل : مدفعية #المقاومة الوطنية تستهدف آليات وموقعًا حو ثيًا في جبهة البرح https://cratersky.support-f0c.workers.dev/posts/237493 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
❤2
دعوة عاجلة بـ #عدن لاجتماع استثنائي بشأن قضية كمال بن شعيلة https://cratersky.support-f0c.workers.dev/posts/237492 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
#عاجل : الكشف عن التفاصيل الكاملة لهجوم الحو ثيين وتطورات الأوضاع العسكرية بـ #تعز https://cratersky.support-f0c.workers.dev/posts/237491 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
#عاجل : قوات #الجيش تعاود السيطرة على مواقع فقدها الحو ثيين https://cratersky.support-f0c.workers.dev/posts/237490 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
❤1
مطالبات بتشغيل منظومة الطاقة الشمسية في مكتب تربية خورمكسر https://cratersky.support-f0c.workers.dev/posts/237489 لمزيد من الاخبار اشتركو بقناتنا على تلجرام http://t.me/cratersky
Showing the 12 most recent of 1,048 posts we hold for @cratersky. 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.
Mentions
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.
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.
Appears in Telegram’s recommendations for other channels
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.
@BoqashEcon · 39,505
Telegram ranks this channel #28 of 70 here — alongside 69 others — read 30 August 2026
@NewsExchange · 33,659
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 4 September 2026
@yemenSul · 52,313
Telegram ranks this channel #35 of 79 here — alongside 78 others — read 24 August 2026
@Exchange_now · 38,481
Telegram ranks this channel #40 of 82 here — alongside 81 others — read 31 August 2026
@ahmedaljoby55 · 51,843
Telegram ranks this channel #77 of 77 here — alongside 76 others — read 24 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“كريتر سكاي” (@cratersky), 14,852 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/cratersky.
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.