Jammu and Kashmir High Court

CCP(S)/342/2022 of MUSHTAQ AHMAD Vs PARVAIZ A. KOUL (SKIMS) (SWP/2523/2018) on 15 September 2026

Cites 0, Cited by 0

No. 27 Regular Cause list HIGH COURT OF JAMMU & KASHMIR AND LADAKH AT SRINAGAR CCP(S) 342/2022 in [SWP 2523/2018] MUSHTAQ AHMAD …Appellant(s)/Petitioners(s) Through: None Vs. PARVAIZ A . KOUL (SKIMS) ...Respondent(s) Through: Ms. Shaila Shameem, Assisting Counsel CORAM: HON’BLE

Serial No. 27

Regular Cause list

HIGH COURT OF JAMMU & KASHMIR AND LADAKH

AT SRINAGAR

CCP(S) 342/2022 in [SWP 2523/2018]

MUSHTAQ AHMAD

…Appellant(s)/Petitioners(s)

Through:

None

Vs.

PARVAIZ A. KOUL (SKIMS)

...Respondent(s)

Through: Ms. Shaila Shameem, Assisting Counsel

CORAM:

HON’BLE MR. JUSTICE RAJESH SEKHRI, JUDGE.

Citations and Judicial Treatment

No citing decisions in the index yet

Cited by

0

Decisions in the index citing it

Cites

0

Decisions referred to

In this index

0

Of the decisions it cites

Overruled / Questioned

0

No negative treatment found

Loading the citing and cited decisions…

ORDER

15.09.2026

1. Learned counsel for the petitioner last appeared on 06.10.2023, i.e., three years back. Since he is continuously absent, it appears that petitioner has lost interest in further prosecution of the case.

2. Hence, present petition is dismissed for non-prosecution, along with connected CMs.

(RAJESH SEKHRI)

JUDGE

Srinagar: 15.09.2026 Adil Ismail

You have used today's free searches. Sign in, for free, to keep searching without a limit.

Compass reads the judgments for you and finds the paragraphs for and against your question. Sign in to use it.

My Vault follows judgments for you and records every later decision that cites them. Sign in to keep one.

Sign in to download the court's PDF. The full text stays free to read here.

Sign in, for free, to download the court copy. Reading the full text here stays open to everyone.

Search and read Indian judgments without limits, save them to My Vault and find the relevant paragraphs with Compass.

Open the sign-in page instead