Channel
@kaisos1987_il
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
5,073subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001305138136 |
|---|---|
| Type | Channel |
| Username | @kaisos1987_il |
| Created | 11 May 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/kaisos1987_il |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 15:44 | 5,073 | -3 |
| 14 Aug 2026, 08:44 | 5,076 | -10 |
| 10 Aug 2026, 21:43 | 5,086 | +5 |
| 7 Aug 2026, 11:16 | 5,081 | no change |
| 7 Aug 2026, 11:03 | 5,081 | first reading |
17 posts held, back to 11 September 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 8 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 17 posts for this entry, the most recent from 12 September 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
54 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 53.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 29 | 53.7% | |
| 👎 | 25 | 46.3% |
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 14 of the 17 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 54reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 11 September 2025 to 12 September 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.
roi kais • روعي كايس • רועי קייס (Twitter) RT @michael_mils: הקביעות החוזרות ונשנות - אחרי כל חיסול של בכירי חמאס - ולפיהן "הוסר מכשול" בדרך לעסקה ומתחזק הסיכוי לפריצת דרך, הן ביטוי לזיכרון הקצר שלנו, וגם לכך ששנתיים אחרי 7 באוקטובר אנחנו עדיין לא מבינים לעומק את הארגון (וגם לא ביקורתיים מספיק כלפי מה שמתקבע אצלנו כ"פסיקות עובדתיות").>> https://twitter.com/kann/status/1924518162277794056#m
👍11👎2
roi kais • روعي كايس • רועי קייס (Twitter) חדש על המדפים בלבנון ובעיראק: ספר של בנו של מנהיג חיזבאללה המחוסל, מוחמד מהדי נסראללה, תחת השם המבטיח "זיכרונות עם אבי" לרגל שנה לחיסולו.
👎8👍1
roi kais • روعي كايس • רועי קייס (Twitter) דיווחנו ביומן הבוקר של @ReshetBet: בעת האחרונה אחד מהנציגים של הכוחות שמתנגדים לחות'ים בתימן העביר מסר לחברי סנאט אמריקניים שהתקיפות הישראליות במתכונתן הנוכחיות בתימן דווקא עלולות להגביר את הפופולאריות של החות'ים, אפילו בקרב מי שסולד מהם בציבור. עוד פרטים 👇
👎3👍1
roi kais • روعي كايس • רועי קייס (Twitter) RT @shemeshmicha: פרסום ראשון: איחוד האמירויות הזמינה את השגריר הישראלי יוסי שלי לשיחת נזיפה ככל הנראה בעקבות התקיפה הישראלית בקטאר. עוד פרטים בהמשך. @kaisos1987
👎2
roi kais • روعي كايس • רועי קייס (Twitter) RT @kann_news: אחרי התקיפה בקטר: שגריר ישראל באמירויות יוסי שלי זומן לשיחת נזיפה https://www.kan.org.il/content/kan-news/politic/950619/ @shemeshmicha @kaisos1987
👎3
roi kais • روعي كايس • רועי קייס (Twitter) RT @mizo_1976: في حديثه للإذاعه اليوم قال @kaisos1987 أن أحد ممثلي القوى المناهضة للحوثيين في اليمن نقل مؤخراً رسالة إلى أعضاء في مجلس الشيوخ الأمريكي، حذّر فيها من أن استمرار الضربات الإسرائيلية بالوتيرة الحالية قد يؤدي إلى زيادة شعبية الحوثيين، حتى بين قطاعات من اليمنيين ممن يعارضونهم.
roi kais • روعي كايس • רועי קייס (Twitter) בלבנון מעדכנים על תקיפה ישראלית לעבר כלי רכב בכפר עייתא אל-ג'בל בדרום לבנון. רגיל
👍2
roi kais • روعي كايس • רועי קייס (Twitter) RT @kann_news: גורמי אופוזיציה בתימן: התקיפות הישראלית מגבירות את התמיכה בחות'ים @kaisos1987
👎2
roi kais • روعي كايس • רועי קייס (Twitter) RT @RZimmt: איראן מבפנים: ניתוח אירועי מחאה ותמיכה במשטר. תוצר אינטראקטיבי חדש של המרכז לאיסוף וניתוח נתונים ב-@INSS_Hebrew. https://www.inss.org.il/he/publication/iran-inside-spotlight/
roi kais • روعي كايس • רועי קייס (Twitter) משרד הבריאות של החות'ים בתימן: 46 הרוגים ו-165 פצועים בתקיפות הישראליות השבוע בבירת תימן צנעא ומחוז אל-ג'ווף הצפוני
👍3
roi kais • روعي كايس • רועי קייס (Twitter) نشر اولي مع @shemeshmicha : بعد الغارة الإسرائيلية في قطر استدعت الامارات السفير الإسرائيلي لدى ابو ظبي يوسي شيلي لاحتجاج على هذا السلوك
👎3
roi kais • روعي كايس • רועי קייס (Twitter) RT @PeaceComCenter: "The concept of 'Kill the Jews' or 'Fight the Jews' must be eliminated." Gazans slam Hamas for brainwashing children and demand education for peace. WATCH:
👎1
Showing the 12 most recent of 17 posts we hold for @kaisos1987_il. 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,531,298 of 1,548,671entries 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.
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.
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.
@kaisos1987_il named 6 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 6 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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“רועי קייס” (@kaisos1987_il), 5,073 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/kaisos1987_il.
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.