Channel
@khorsanchronicles
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
237subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003981920702 |
|---|---|
| Type | Channel |
| Username | @khorsanchronicles |
| Created | Between 1 April 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/khorsanchronicles |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:57 | 237 | +6 |
| 10 Sept 2026, 17:59 | 231 | +1 |
| 31 Aug 2026, 21:14 | 230 | +1 |
| 24 Aug 2026, 23:06 | 229 | -4 |
| 16 Aug 2026, 17:24 | 233 | +7 |
| 8 Aug 2026, 10:19 | 226 | no change |
| 8 Aug 2026, 05:16 | 226 | +1 |
| 7 Aug 2026, 19:09 | 225 | first reading |
20 posts held, back to 2 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 20 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 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 64.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 9 | 64.3% | |
| 🔥 | 3 | 21.4% | |
| 👍 | 2 | 14.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 9 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 14 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 2 August 2026 to 8 August 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.
پولیس تشدد اور کراچی کے شفیق مور میں پشتون کاروباروں کو نشانہ بنانا آج رات شفیق مور، کراچی پر پشتون چائے خانوں، گاڑیوں اور دکانداروں کو پولیس کی وحشیانہ بدعنوانی کا سامنا کرنا پڑا، جس میں اغوا اور رہائی کی درخواست شامل تھی۔ حالیہ مہینوں میں سندھ پولیس نے مبینہ طور پر کئی پشتونوں کو حراست میں لیا ہے، دکانیں اور گاڑیاں ضبط کی ہیں، اور رہائی سے پہلے ادائیگی جبری کی ہے۔ @khorsanchronicles
Police violence and extortion targeting Pashtun businesses on Shafiq Mor, Karachi Tonight on Shafiq Mor, Karachi, Pashtun tea shops, carriages and vendors faced brutal police misconduct, including abductions and demand-for-release payments. In recent months Sindh Police have reportedly detained many Pashtuns, seized shops and vehicles, and forced payments before release. @khorsanchronicles
🤬1
راولپنڈی میں پولیس تشدد اور اغوا کے الزامات — خواتین نے کارروائی کا مطالبہ کیا سنگین الزامات سامنے آئے ہیں کہ راولپنڈی میں خواتین کو پولیس اہلکاروں نے مارا پیٹا جبکہ ایک بہن بھائی کو مبینہ طور پر اغوا کیا گیا۔ جب ایک خاتون صوبے کی وزیر اعلیٰ کے طور پر خدمات انجام دے رہی ہیں، تو عوام پوچھتے ہیں: حکومت متاثرین کی تحقیقات اور تحفظ کے لیے کیا اقدامات کر رہی ہے؟ @khorsanchronicles
Allegations of Police Violence and Kidnapping in Rawalpindi — Women Demand Action Serious allegations have emerged that women in Rawalpindi were beaten by police officers while a sibling was reportedly abducted. With a woman serving as the province’s chief minister, the public asks: what steps is the government taking to investigate and protect victims? @khorsanchronicles
🤬1
کوئٹہ-تفتان ہائی وے پر متعدد حملے ہوئے؛ انفراسٹرکچر اور ٹرانسپورٹ کو ہدف بنایا گیا کوئٹہ-تفتان ہائی وے پر پیر کو مسلسل حملے کا سامنا کرنا پڑا، جس میں مسلح حملہ آوروں نے پانچ مربوط حملے کیے۔ اہداف میں پاکستانی فوجی قافلے، کارگو اور معدنیات کی نقل و حمل کی گاڑیاں، اور ایک پل شامل تھے جو دھماکے سے تباہ ہو گیا، جس سے راستے میں نقل و حرکت اور تجارت متاثر ہوئی @khorsanchronicles
Quetta–Taftan Highway struck by multiple attacks; infrastructure and transport targeted Quetta–Taftan Highway came under sustained attack Monday, with armed assailants carrying out five coordinated strikes. Targets included Pakistani military convoys, cargo and mineral transport vehicles, and a bridge that was blown up, disrupting movement and trade along the route @khorsanchronicles
🔥2
راولپنڈی پرس کلب کے قریب کم از کم 60 طلبہ حراست میں لے لیے گئے رپورٹس کے مطابق 60+ طلبہ کو راولپنڈی پرس کلب کے باہر حکام کے ساتھ تصادم کے دوران گرفتار کیا گیا۔ اجتماع کی وجہ، زخمیوں اور سرکاری بیانات کی تفصیلات محدود ہیں @khorsanchronicles
At Least 60 Students Detained Near Rawalpindi Purse Club Reports say 60+ students were arrested outside the Rawalpindi Purse Club during a confrontation with authorities. Details about the cause of the gathering, injuries, and official statements remain limited @khorsanchronicles
🤬2
رپورٹس کے مطابق پاکستانی فورسز نے کشمیر میں شہریوں پر براہ راست فائرنگ کی ہے متعدد رپورٹس سے پتہ چلتا ہے کہ پاکستانی سیکیورٹی فورسز نے کشمیر کے کچھ حصوں میں شہریوں کے خلاف زندہ گولہ بارود استعمال کیا ہو سکتا ہے، اور سنگین انسانی حقوق کی خلاف ورزیوں کے الزامات سامنے آئے ہیں @khorsanchronicles
Reports allege Pakistani forces have used live fire against civilians in Kashmir Multiple reports indicate that Pakistani security forces may have used live ammunition against civilians in parts of Kashmir, with allegations of serious human rights violations emerging @khorsanchronicles
👍2🤬2
سکیورٹی فورسز نے مظفرآباد میں مظاہرین کی موٹر سائیکلیں جلا دیں مظفر آباد کی رپورٹس کے مطابق آج جھڑپوں کے دوران سیکیورٹی فورسز نے کئی مظاہرین کی موٹر سائیکلوں کو آگ لگا دی، متعدد عینی شاہدین اور مقامی ذرائع کے مطابق۔ اس واقعے نے کشیدگی کو بڑھا دیا ہے کیونکہ مظاہرین اور قانون نافذ کرنے والے ادارے شہر کی سڑکوں پر ایک دوسرے کے خلاف آپس میں آمنے سامنے آ رہے ہیں۔ @khorsanchronicles
Security forces burn protesters' motorcycles in Muzaffarabad Reports from Muzaffarabad say security forces set fire to several protesters' motorcycles during clashes today, according to multiple eyewitness accounts and local sources. The incident has heightened tensions as demonstrators and law enforcement confronted each other in city streets. @khorsanchronicles
🤬1
Showing the 12 most recent of 20 posts we hold for @khorsanchronicles. 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.
Named by 2 registered channels — 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Khorsan Chronicles” (@khorsanchronicles), 237 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/khorsanchronicles.
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.