Channel
@centerkaf
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
41,628subscribers
-716 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001072345716 |
|---|---|
| Type | Channel |
| Username | @centerkaf |
| Description | كاف منصة الكترونية تابعة للإعلام الحربي للمقاومة الاسلامية في العراق . |
| Created | 21 October 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/centerkaf |
Politics & activism — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
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.
23,700 average views per post against 41,628 subscribers — an engagement rate of 56.9%. Across the 2,056 registered channels in the same cohort — 31,636–99,983 subscribers, posting mainly in Arabic — the middle half sit between 1.59% and 11.3%, with a median of 5.10%.
| Window | 30 days (13 September 2026 – 13 October 2026) |
|---|---|
| Posts measured | 43 of 43 published in the window (0 exact, 43 rounded by Telegram) |
| Views totalled | 1,018,440 |
| Mature posts only | 62.8% over 38 posts read at least 24h after publication |
| Subscribers | 41,628 measured 13 October 2026 |
| Cohort | b31623:ara · 2,056 channels · p10 0.385% · p25 1.59% · p50 5.10% · p75 11.3% · p90 20.4% |
| Position in cohort | 99.367th percentile · 11.2× the cohort median |
| Uncertainty | ±0.081% of the figure, from Telegram’s rounding |
| Post language | Arabic · 94.9% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 13 October 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 13:29 | 41,628 | -43 |
| 9 Oct 2026, 15:38 | 41,671 | -150 |
| 5 Oct 2026, 07:42 | 41,821 | +106 |
| 28 Sept 2026, 23:58 | 41,715 | -208 |
| 17 Sept 2026, 19:01 | 41,923 | -65 |
| 15 Sept 2026, 15:02 | 41,988 | -118 |
| 13 Sept 2026, 20:39 | 42,106 | -129 |
| 12 Sept 2026, 02:58 | 42,235 | +33 |
| 9 Sept 2026, 22:02 | 42,202 | -35 |
| 6 Sept 2026, 12:17 | 42,237 | -82 |
| 4 Sept 2026, 06:19 | 42,319 | -49 |
| 2 Sept 2026, 17:55 | 42,368 | -12 |
| 1 Sept 2026, 18:03 | 42,380 | -22 |
| 31 Aug 2026, 19:35 | 42,402 | -13 |
| 30 Aug 2026, 16:44 | 42,415 | -2 |
| 29 Aug 2026, 15:44 | 42,417 | -49 |
| 28 Aug 2026, 17:42 | 42,466 | -40 |
| 27 Aug 2026, 19:07 | 42,506 | +27 |
| 26 Aug 2026, 16:09 | 42,479 | +121 |
| 25 Aug 2026, 16:23 | 42,358 | first reading |
87 posts held, back to 16 July 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 130 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 October 2026 |
|---|---|
| Posts held | 87 (16 July 2026 – 12 October 2026) |
| Views total | 1,018,440 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Oct 2026, 17:14 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.
Lifetime counters from Telegram’s own channel header, read 13 October 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 34 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.
🔴 الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. يستمر العدو في انتهاكه الصارخ لسيادتنا الجوية، انطلاقا من قواعدهم في الأردن والاراضي المحتلة. - طائرات (KC-135) عدد 2. - طائرة (F35) عدد 1. - طائرة (E-11) عدد 1. 🔻 يوم الأحد 11-10-2026
بسم الله الرحمن الرحيم (وَلَا تَهِنُوا وَلَا تَحْزَنُوا وَأَنتُمُ الْأَعْلَوْنَ إِن كُنتُم مُّؤْمِنِينَ) نبارك للإخوة في يمن الصمود، شعبًا وقيادة، العمليات العسكرية للدفاع عن كرامة شعبه وحقوقه المسلوبة، إثر الحصار المفروض عليه من الكيان السعودي، وبدعمٍ من العدو الصهيوأمريكي وأدواته في المنطقة. وفي الوقت الذي ندعو فيه محمد بن سلمان وأسياده إلى قبول الهزيمة ورفع الحصار الظالم عن شعب اليمن، نؤكد أن الشعب العراقي ومقاو…
🔴 الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. يستمر العدو في انتهاكه الصارخ لسيادتنا الجوية، انطلاقا من قواعدهم في الأردن والاراضي المحتلة. - طائرات (KC-135) عدد 5. - طائرات (F16) عدد 2. - طائرات (F35) عدد 2. - طائرة مسيرة (MQ9) عدد 1. طوال ساعات يوم السبت 10-10-2026 .
🔴 الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. يستمر العدو في انتهاكه الصارخ لسيادتنا الجوية، انطلاقا من قواعدهم في الأردن وتركيا والاراضي المحتلة والكويت والسعودية. طوال ساعات يوم الخميس 8-10-2026 .
🔴 الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. يستمر العدو الأمريكي في انتهاكه الصارخ لسيادتنا الجوية، انطلاقا من قواعدهم في الأردن. - طيران حربي نوع (F-35) عدد 1. - طائرة تزود بالوقود (KC-135) عدد 2 . - طائرات مسيّرة (MQ9) عدد 4 . طائرة مسيّرة (MQ1) عدد 1. طوال ساعات يوم الاربعاء 7-10-2026 .
اذا استيقظت ارادة الاحرار تهاوت رموز الجبروت وبقيت الكرامة شاهدة ان للارض رجال.
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. يستمر العدو الأمريكي في انتهاكه الصارخ لسيادتنا الجوية، انطلاقا من قواعدهم في الأردن. فقد حامت ثلاث طائرات مسيرة من طراز MQ9 – وطائرة مسيرة من طراز MQ1 وطائرة التزود بالوقود KC135 فوق سماء مدن بغداد والانبار والبصرة وجنوب غرب العراق. طوال ساعات يوم الثلاثاء 6/10/2026 .
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. الرصد بتأريخ 5-10-2026
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. الرصد بتأريخ 4-10-2026
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية.
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية. الرصد بتأريخ 1-10-2026
🔴الرصد اليومي لطلعات العدو الجوية التي يخرق بها السيادة العراقية.
Showing the 12 most recent of 87 posts we hold for @centerkaf. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 57 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“كاف - Kaf” (@centerkaf), 41,628 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/centerkaf.
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.