Fuel price history in Pakistan
Every entry below corresponds to an official OGRA / Finance Division notification, verified against OGRA — Oil & Gas Regulatory Authority. Prices are the ex-depot consumer maximum in PKR per litre.
Petrol vs. one year ago
+PKR 63.52/L
HSD vs. one year ago
+PKR 99.71/L
| Effective from | Petrol (PKR/L) | HSD (PKR/L) | Petrol Δ | HSD Δ |
|---|---|---|---|---|
| 18 July 2026 | 316.15 | 354.35 | +5.44 | +31.05 |
| 11 July 2026 | 310.71 | 323.30 | +43.92 | +50.32 |
| 1 July 2026 | 266.79 | 272.98 | 0.00 | 0.00 |
| 16 June 2026 | 266.79 | 272.98 | +8.36 | +10.39 |
| 1 June 2026 | 258.43 | 262.59 | +5.80 | +7.95 |
| 16 May 2026 | 252.63 | 254.64 | — | — |
How to read this history
The Government of Pakistan revises petroleum prices on the 1st and 16th of every month. The value in each row is the ex-depot consumer maximum notified by OGRA; the number your fuel station is legally allowed to charge before local dealer margin adjustments. The Δ (delta) columns show the change from the previous fortnight — a positive figure in red means prices rose, a negative figure in green means they fell.
What drives the fortnightly change
Three inputs move the number. First, the Platts Arab Gulf price for the reference product (motor spirit for petrol, gasoil for HSD) averaged over the previous 15 days. Second, the PKR/USD parity used to convert that dollar price into rupees — a two-rupee move on the dollar typically translates into roughly a 1.5–2 rupee per litre change at the pump. Third, the Petroleum Development Levy (PDL) and sales tax rate for the fortnight, which the Finance Division can raise or lower to buffer the international price change.
Methodology & sourcing
Every row in this table is entered manually from the OGRA notification PDF, re-verified against the Finance Division press release, and cross-checked against the PSO tariff for the same effective date. We do not include prices from unofficial resellers, media speculation, or leaked "expected" figures. Corrections to any historical value are logged with the timestamp of the fix on our editorial policy page.