TODAY’S PAPER | November 22, 2026 | EPAPER

Tribal clash over land leaves seven dead

Four members of Gilal tribe, three from Kohistani community killed


IRSHAD NASHAD November 22, 2026 1 min read

BATTAGRAM:

A longstanding dispute between the Kohistani and Gilal tribes in the mountainous Balija Chor area of Allai tehsil in Battagram district has intensified, leaving seven people dead and two others injured in an exchange of fire between the two sides.

According to police sources, the Kohistani and Gilal tribes have been involved in a dispute over the area for several years.

On the night between Friday and Saturday, members of the Kohistani tribe allegedly attempted to set fire to the properties of the Gilal tribe. The latter resisted, triggering an exchange of fire between the two sides. As a result, four members of the Gilal tribe and three from the Kohistani community were killed, while one person sustained serious injuries.

The deceased belonging to the Gilal tribe were identified as Gul Bakhti, son of Tale, Sarfaraz, son of Bogla, Hussain Khan, son of Gul Rehman, and Khan, son of Muhammad Sattar, all residents of Tandol, Allai.

Farhat, son of Malik, was seriously injured in the incident.

The names of the three people killed from the Kohistani tribe could not be ascertained.

Meanwhile, the relatives of the deceased from Tandol, Allai, brought the bodies to Bana Bazaar, the tehsil headquarters, and placed them on the road in protest. They refused to bury the bodies until justice was ensured.

During the protest, administrative officials, including the Assistant Commissioner Allai and the Deputy Superintendent of Police, arrived for negotiations.

Following assurances from the officials that justice would be provided to the bereaved families, the protesters called off their demonstration.

On the occasion, the jirga also announced that it would decide its future course of action on Monday.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ