Army soldier killed in Indian firing along LoC

ISPR says 20-year-old sepoy was a resident of Shanglot village in Ghizer district

Web Desk September 15, 2015
A file photo of Indian security forces across the LoC. PHOTO: AFP

RAWALPINDI: A Pakistan Army soldier was killed on Tuesday as India’s Border Security Force (BSF) resorted to unprovoked firing along the Line of Control (Loc) in Battal Sector.

“Sepoy Shams embraced martyrdom,” an Inter Services Punlic Relations (ISPR) statement said.

“The 20-year-old sepoy was a resident of Shanglot village in Ghizer district of Gilgit-Baltistan,” it added.

Further, ISPR said, “Pakistani troops responded befittingly to Indian unprovoked firing.”

Read: Indian troops violate ceasefire in Nakial sector

Just days after Pakistan Rangers and Indian Border Security Force (BSF) agreed to stop ceasefire violations, Indian troops yet again violated the Line of Control (LoC) on Monday evening.

According to an Inter Services Public Relations (ISPR) statement, Indian troops resorted to unprovoked shelling and firing in Nakial sector.

Both the countries had agreed on Saturday to restore ceasefire at the working boundary to save lives of innocent civilians. However, violations continue unabated.

The breakthrough came at the bi-annual meeting between Pakistan Rangers and Indian BSF, which was held under a ‘cordial atmosphere’ with both sides also agreeing to carryout joint investigations of future ceasefire violations.


Ravi | 5 years ago | Reply @Gul: Your comments are appreciated. I am wondering if the news of yesterday's martyrdom of an Indian Army Major by the Pakistan forces was ever reported in the Pakistani media. There are no winners here, only losers - on both sides of the border.
Gul | 5 years ago | Reply Yesterday we killed an Indian soldier. Now revenge. This madness should stop. Only the poor people and poor soldiers suffer. Not the elite who perpetuate conflict.
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