eyesonkashmir.com
verified by Jammu Kashmir Human Rights Observatory, as of August 6, 2026
reported, not yet confirmed by that monitor
These are separate counts, not attempts at the same one, and they are deliberately left unreconciled. The monitor's figure is a verified civilian count; any report figure is what one outlet said on one day; authorities dispute the higher tolls. No tracked event currently carries its own death figure for this region, so only the monitor's count is shown. Source for the documented figure
A live, source-based map of events across Kashmir, on every side of the Line of Control. It shows what is being reported, who reported it, and where accounts disagree. It does not, however, tell you who is right.
Situation summary · as of 18 August 2026
On 7 June 2026 a long-running set of economic and political grievances in Pakistan-administered Kashmir turned into mass protests. The movement is led by the Jammu Kashmir Joint Awami Action Committee, which put a 38 point charter of demands to the Azad Jammu and Kashmir government: cheaper electricity and flour, an end to privileges for politicians and officials, and changes to how the territory is governed.
The sharpest demand concerns the 12 seats in the AJK Legislative Assembly reserved for refugees from Jammu and Kashmir who live elsewhere in Pakistan. Protesters argue those seats let people outside AJK shape its government and hand Pakistan's national parties outsized influence over local politics.
The government banned the committee under anti-terrorism law, arrested organisers and deployed security forces. Protests continued and the clashes grew deadlier. By mid June an AFP tally based on official figures put the dead at 20.
Violence peaked around the regional elections in early August, with running battles in Rawalakot. The Jammu Kashmir Human Rights Observatory says it has verified 89 civilian deaths since 7 June, with four more still being checked, and records 49 of them between 27 July and 5 August, including 38 in Rawalakot. Police and government officials dispute those tolls and say armed men among the protesters attacked security forces. The Human Rights Commission of Pakistan has called for an impartial, independent investigation into the Rawalakot deaths.
Every figure above belongs to whoever published it. None of them is settled, independent verification on the ground remains limited, and that is the reason this site records claims and their claimants rather than a single number.
Everything on the map above comes from what outlets chose to publish. That leaves out most of what actually happened: the call that would not connect, the queue at the hospital, the shop that stayed shut for a fortnight, the relative nobody has heard from. If you live in Kashmir, if your family is there, or if your work takes you there, you hold part of this record that no wire service will ever carry.
You do not need to be a journalist and you do not need proof. Write it in whatever language you think in. A person reads every account, nothing is published without your permission, and accounts are kept separate from the event feed because testimony and a corroborated report are not the same thing.
Nobody has written in yet
No accounts have been published yet, so this column is empty. That is not a shortage of things worth saying. It means nobody has been asked, or nobody thought it would count.
Yours would be the first entry in the record.
Prefer email? Write to arslaanjuga00@gmail.com
Every 10 minutes the collector sweeps 30 feeds. Deterministic code does the work it can do reliably; a language model is used only where judgement is genuinely required, and never to decide what is true.
This is an open-source website. The collector, the clustering, the claim model and this page are all readable code, and the project takes contributions. For access to the codebase, or to propose a change, a source, or a correction, write to arslaanjuga00@gmail.com.
RSS and targeted news search across every ecosystem covering the region.
URL canonicalisation and headline fingerprints drop re-publishes.
A gazetteer of 90+ Kashmiri places gates what is actually regional.
Category, location, severity, and every claim with its claimant.
Reports of one incident merge into a single event with a source list.
Independence scored across ecosystems, then published or held.
Autonomy is scoped by how much harm a wrong call would do. The higher the stakes, the more corroboration the system demands before anything reaches the public map.
Infrastructure, weather and disasters, health, elections, routine politics and diplomacy. Low cost if a label is wrong, easy to correct.
Protests, humanitarian conditions, communications blackouts, displacement. Published with an explicit verification state so a single-source report never reads as settled.
Armed clashes, LoC firing, militant attacks, security operations, casualty claims. Released only once independent sources from at least two ecosystems agree. Otherwise it waits in a human review queue.
Corroboration only counts when it crosses ecosystems. Four outlets from the same media environment carrying one story is repetition; a Pakistani outlet, a Kashmiri outlet and a wire agreeing is confirmation.