⭕️ سمیر ابو یونس، فرمانده تیپ رفح در گردانهای قسام حماس اندکی پیش توسط نیروهای دفاعی اسرائیل ترور شد و کیر شد 🔥 @Ontweet
🤣12🔥7👍1

Channel
@ontweet
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
8,150subscribers
-266 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001127629384 |
|---|---|
| Type | Channel |
| Username | @ontweet |
| Description | اسپانسر ما: 🆔 @Movie_Vpn (پرسرعت V2Ray🔥) استوری و توییت :) با فوروارد پست ها از ما حمایت کنید.💜 استوری هارو با سرچ هشتگ #استوری پیدا کنید🔥❤ 🔗 Instagram: instagram.com/movie_facts_farsi @TalkTalent (کانال معرفی فیلم) @MovieFact_DL (گروه لینک ها) |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/ontweet |
National news — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 14:35 | 8,150 | -13 |
| 7 Nov 2026, 07:56 | 8,163 | -1 |
| 3 Nov 2026, 21:01 | 8,164 | -4 |
| 1 Nov 2026, 03:39 | 8,168 | -10 |
| 29 Oct 2026, 11:35 | 8,178 | -4 |
| 26 Oct 2026, 04:10 | 8,182 | -1 |
| 23 Oct 2026, 03:06 | 8,183 | +5 |
| 20 Oct 2026, 11:46 | 8,178 | -5 |
| 17 Oct 2026, 21:29 | 8,183 | -1 |
| 15 Oct 2026, 00:50 | 8,184 | -5 |
| 12 Oct 2026, 04:39 | 8,189 | -17 |
| 5 Oct 2026, 06:17 | 8,206 | -37 |
| 27 Sept 2026, 01:02 | 8,243 | -18 |
| 18 Sept 2026, 06:39 | 8,261 | -16 |
| 14 Sept 2026, 01:02 | 8,277 | -9 |
| 9 Sept 2026, 22:37 | 8,286 | +1 |
| 4 Sept 2026, 19:17 | 8,285 | +6 |
| 1 Sept 2026, 07:28 | 8,279 | -12 |
| 29 Aug 2026, 18:14 | 8,291 | -13 |
| 27 Aug 2026, 01:44 | 8,304 | first reading |
333 posts held, back to 4 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 47 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 14 November 2026 |
|---|---|
| Posts held | 333 (4 August 2026 – 14 November 2026) |
| Views total | 254,075 |
| Reactions total | 6,131 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 02:56 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 15 November 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 21 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.
14,778 reactions across 323 posts, in 27 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 4,635 | 31.4% | |
| 🔥 | 3,331 | 22.5% | |
| 👍 | 2,255 | 15.3% | |
| 😁 | 900 | 6.09% | |
| 🤬 | 874 | 5.91% | |
| ❤ | 858 | 5.81% | |
| 💔 | 703 | 4.76% | |
| 👏 | 406 | 2.75% | |
| 🍾 | 123 | 0.832% | |
| 😱 | 106 | 0.717% | |
| 😡 | 92 | 0.623% | |
| 😢 | 64 | 0.433% | |
| 🎉 | 58 | 0.392% | |
| 😭 | 53 | 0.359% | |
| 😍 | 50 | 0.338% | |
| 😐 | 46 | 0.311% | |
| 💯 | 45 | 0.305% | |
| 👎 | 43 | 0.291% | |
| 🤔 | 37 | 0.25% | |
| 🗿 | 35 | 0.237% | |
| 7 further kinds | 64 | 0.433% |
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 333 of the 333 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 15,076 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 333 most recent posts we hold, published 4 August 2026 to 14 November 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.
Telegram’s own ‘edited’ marker: 18 of 145 posts held from the last 30 days (12.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
⭕️ سمیر ابو یونس، فرمانده تیپ رفح در گردانهای قسام حماس اندکی پیش توسط نیروهای دفاعی اسرائیل ترور شد و کیر شد 🔥 @Ontweet
🤣12🔥7👍1
⭕️ کمتر از 36 ساعت آینده، برای اولین بار بعد از حمله آمریکا به عراق، سه ناو هواپیمابر ارتش آمریکا در خاورمیانه مستقر خواهند شد. @Ontweet
🔥17👍1💘1
یه گونی ام می کشیدی رو سرت بی خایه 😂 @Ontweet
🤣42🍾1🏆1
🚨 جسد ارغوان احمدیان، سرکردهی بسیج فرهنگیان شوشتر، بعد از دو روز بیخبری کنار جاده شوشتر به کوشکک پیدا شد. طبق گزارشها با شلیک گلوله کتلت شده @Ontweet
🎉50🔥16🥰2😢2💯1🤣1
❌ منابع عبری : آیزنکوت پس از جلسه با نتانیاهو از طرح حمله به جمهوری اسلامی استقبال کرده فقط دلش می خواد توی اتفاقات آینده نقشی داشته باشه به احتمال زیاد به زودی شاهد تشکیل یک دولت وحدت ملی به رهبری نتانیاهو و نقش پر رنگ آیزنکوت باشیم @Ontweet
👍33❤4
⭕️ نتانیاهو : ایران در حال تلاش برای ساخت سلاح های هسته ای است و باید با تشکیل دولت وحدت ملی جلوی ایران را بگیریم بیایید کاری که لازم است در قبال ایران انجام دهیم و کار را یکبار برای همیشه تمام کنیم @Ontweet
🔥23👍5👎2❤1
با افزایش نرخ بنزین و کمبود سوخت قیمت الاغ به 300 میلیون افزایش پیدا کرد. @Ontweet
🤣38🤬1
شباهت چُس با مجتبی اینه که جفتشون نه صدا دارن نه دیده میشن. Nima @Ontweet
🤣59👍2💯1
ناو روزولت به ۸۰۰ کیلومتری ایران رسید ⭕️ ناوگروه هواپیمابر روزولت تا ۳۶ ساعت آینده درحالت عملیاتی قرار خواهد گرفت @Ontweet
🔥39👍4❤2
⭕️ گادی آیزنکوت : هیچگاه با منصور عباس(رهبر احزاب عربی) ائتلاف نمیکنم، دولتی که قراره تشکیل بدم، تماماً اسراییلی خواهد بود، حتی از حزب لیکود و نتانیاهو هم لازم باشد کمک خواهم گرفت @Ontweet
👍48❤4
🔴 مارکو روبیو، وزیر امور خارجه آمریکا: جمهوریاسلامی دهها هزار نفر از مردم خودش رو کشته. اونا تو خیابونا مردم رو قتلعام کردن. اگه زخمی بشید، به بیمارستانا میان و شما رو روی تخت بیمارستان به قتل میرسونن و پزشکا و پرستارایی رو هم که به شما رسیدگی کردن رو میکشن. این کاریه که اونا با مردم خودشون میکنن. حال تصور کنید اگه سلاح هستهای داشته باشن، با ما چیکار میکنن. @Obtweet
👍83❤4👎1
⭕️دهها هواپیما در نیویورک روی زمین و پیش از برخاستن قرار دارند. تنها پروازهایی که در حال فرود هستند، همچنان در فضای هوایی در حال چرخشاند برخی معتقدند که در ایالات متحده، هم اکنون تمرینات نظامی بسیار بی سابقه ای در حال انجام است و در آنها، پروتکلهای خاصی برای شرایط بسیار اضطراری تمرین داده میشوند هنوز هیچ نهاد رسمی دلیل این اتفاقات بیان نکرده @Ontweet
🔥20❤3👍1
Showing the 12 most recent of 333 posts we hold for @ontweet. 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.
We recorded 1 post on @ontweet as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
@ontweet named 1 handle 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 2 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“OnTweet” (@ontweet), 8,150 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/ontweet.
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.