West India · ranked #7 of 25

Gujarat

5 examinations conducted in or for Gujarat are recorded here as compromised between 2019 and 2023, of which 4 were officially confirmed.


Incidents
5
2019–2023
Confirmed
4
80% of the total
Candidates affected
10.5lakh
reported in 3 incidents
Exams voided
3
cancelled or re-held
Arrests recorded
33
across 2 incidents
Bodies involved
4
examination authorities

Incidents per year

Shown against the full 2004–2026 range so gaps are visible.

  • Confirmed
  • Alleged
  • Suspected
  • Denied

An empty year means nothing is recorded here for that year — not necessarily that nothing happened.

Show the numbers
YearConfirmedAllegedSuspectedDeniedTotal
201910001
202120002
202201001
202310001

Bodies involved

  • GSSSB State 2
  • GPSSB State 1
  • Gujarat University / Forest Dept State 1
  • Indian Railways (RRB / RRC) Central 1

The record

Every Gujarat incident

Showing 5 incidents. Select any row for the full record.

Documented Indian examination leak incidents, sortable by column.
Outcome
29 Jan 2023GPSSB Junior Clerk recruitment exam
GPSSB · State
Gujarat Confirmed199.5L Cancelled FIR
27 Mar 2022Forest Guard recruitment exam
GU / Forest · State
Gujarat Alleged FIR
12 Dec 2021Head Clerk recruitment exam
GSSSB · State
Gujarat Confirmed1488k Cancelled FIR
3 Jan 2021Railway GDCE 2021 (General Departmental Competitive Exam, RRC Mumbai)
Railways · Central
Gujarat Confirmed8.6k FIR Probe
17 Nov 2019Non-Secretariat Clerk recruitment exam
GSSSB · State
Gujarat Confirmed Cancelled

Open data · CC BY 4.0

This record is incomplete. Help finish it.

Every row here is one news report away from being verifiable — and there are leaks we have certainly missed, especially state recruitment exams before 2015 and cases reported only in regional-language press. The dataset is one CSV file. Adding to it takes a pull request.

1 Find a source. A named news report, court order, official notice or RTI reply. One incident, one primary link.
2 Add one row to exam_leaks.csv. Leave a field blank rather than guessing it.
3 Open a pull request. A preview build validates the row; a maintainer checks the source against the claim.
4 Not a coder? Open an issue with the link and we will transcribe it for you.