Channel
@kochizakarni
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,454subscribers
-69 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001817962691 |
|---|---|
| Type | Channel |
| Username | @kochizakarni |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/kochizakarni |
Politics & activism — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 |
|---|---|---|
| 18 Sept 2026, 23:37 | 1,454 | -9 |
| 14 Sept 2026, 04:59 | 1,463 | -2 |
| 10 Sept 2026, 15:41 | 1,465 | -4 |
| 5 Sept 2026, 08:17 | 1,469 | -8 |
| 1 Sept 2026, 20:43 | 1,477 | -5 |
| 29 Aug 2026, 12:37 | 1,482 | -5 |
| 26 Aug 2026, 20:11 | 1,487 | -7 |
| 24 Aug 2026, 00:28 | 1,494 | -4 |
| 20 Aug 2026, 13:33 | 1,498 | -4 |
| 17 Aug 2026, 10:16 | 1,502 | -11 |
| 13 Aug 2026, 23:26 | 1,513 | -6 |
| 10 Aug 2026, 14:55 | 1,519 | -2 |
| 7 Aug 2026, 21:34 | 1,521 | no change |
| 7 Aug 2026, 19:21 | 1,521 | -2 |
| 7 Aug 2026, 16:28 | 1,523 | first reading |
20 posts held, back to 4 April 2025 — 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 16 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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.
250 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 87.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 219 | 87.6% | |
| 💔 | 31 | 12.4% |
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 20 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 250 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 4 April 2025 to 16 May 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.
صَالح الزكارنة صَاحب الابتسامة، والوَجه الحَسّن، الَّذي نَال مِن اسمه نصيبًا المُلقب بالكوشي، شابٌّ ترعرع عَلى الجِهاد فِي سَبيلِ الله وحبِّ الدِّين والوطن، مُجدد الاشتباك وصَانع العبوات فِي قَباطية الَّتي نُحبها، مَا أعظَم صَنيعك، فأنّتَ فخرٌ لهذه الأمة وعِزُّها، ستُسطر بُطولاتك فِي كتب التَّاريخ، وَسيبقى اسمك محفورًا فِينا، كانَ صَالح أسيرًا ثم مُصابًا ثم شهيدًا، صنع لِلوطن المَجد والحرية، ورَحلَ تاركًا خَلفه جيلًا…
❤8
ستَظلُّ في ذاكِرتنا أبَدًا فأنتَ قِصّة بُطوليّة تَروِيها شَهامةٌ وفِداء 🖤.
❤7
روحٌ ورَيحان ورَوضٌ وجِنان وشربةٌ من يَدي نبِينا العدنَان ونعيمٌ مقيمٌ بِـ جوارِ الرَّحمن 💔.
❤7
السّلَامُ عَلى مَن كَانت رَاحته فِي مَيادِين الجِهَاد ،رَحِم اللّٰه من كَان أوّل المتَصدّين للإقتِحَام إلى رِضوان اللّٰه مُقبل غير مُدبر، ذِكرَى سيد الرِجَال " الشَّهِيد صالح زكارنة ( الكُوشي ) ."
❤10
اللهُمَّ إن هذا مَطر رحمتك، فاجعل شهيدنا في رحمتك التي وسعت كل شيء، اللهم نوّر قبوره، وارفع ذكره، واكتب له حياةً عندك لا موت بعدها، واجعل لقاءهُ بك لقاءَ رضا وكرامة، واسقِ روحهُ من حوض نبيك شربةً لا يظمأ بعدها أبدًا 🤍.
❤11
اللهُمَّ إرحَم مَن كانَ يقَاتل فِي ساحاتِ المِيدان، اللهُمَّ إجعلهُ مِن أسعَد السُّعداء ضاحِكاً مُستَبشراً فِي جنّات النَّعيم.
❤10
﴿ مِّنَ الْمُؤْمِنِينَ رِجَالٌ صَدَقُوا مَا عَاهَدُوا اللَّهَ عَلَيْهِ ﴾ 🖤.
❤9
أوجَعتَنا والدَّمعُ محبُوسٌ ضَريرّ فارَقتنَا لكنَّ نجمكَ مُستَنيرّ 💔.
❤8💔1
إن رَحلَ الجَسدُ، فَذكراهُ باقيةٌ لاَ تموتُ.
❤9
اللهُمَّ اجعل دَمه الطَاهر نوراً يضِيء لهُ طَريق الجنَّة، وتقبّلهُ قبولاً حسناً وَجعل روحهُ فيِ نعيمٍ لا يزول، وَقبره روضةً مِن رِياض الجنَّة، ونوّر وَجهه بِنور رضَاك 🤍.
❤9
إِنَّما والله تَبكي العَين عَلى مَنِ لا يَأْتي الزَّمانِ بمثله، نِصف عَام على رَحيل بَطلنا صالِح💔.
💔11
يَا حَظ من جعلَ الشَّهادة منِيَّة وَمشي بركب الصَّادقين مُهَاجِراً .
❤13
Showing the 12 most recent of 20 posts we hold for @kochizakarni. 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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“الكُوشي🖤🥷🏻.” (@kochizakarni), 1,454 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kochizakarni.
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.