Bengaluru is sitting on a Rs 1,425 crore pile of unpaid traffic challans — the largest single-city share inside Karnataka's Rs 1,700 crore state backlog of more than 3.25 crore uncleared violations. The reason this matters for a used car buyer, especially one shopping in the IT corridors of Whitefield, Electronic City, Marathahalli or Sarjapur or buying a Bengaluru-registered vehicle from a reseller in Mysuru, Mangalore, Hubli or Belagavi, is structural. Every one of those challans is tagged to a registration number, not to the person who committed the offence. When the seller leaves the city or simply changes phones, the challan sits silently on the RC. When the buyer arrives at the RTO counter to complete Form 28, 29 or 30, the file freezes. The bill that surfaces is paid by whoever is holding the keys at that moment.
The Rs 1,425 Crore Bill Bengaluru Has Not Paid
The Rs 1,425 crore figure for Bengaluru — reported by Deccan Herald as part of a wider review of Karnataka's traffic enforcement ledger — works out to roughly 84 per cent of the state's total unpaid challan pool. The state-level number sits at Rs 1,700 crore, with more than 3.25 crore individual violations still in pending status. Put differently, the rest of Karnataka combined — Mysuru, Mangalore, Hubli-Dharwad, Belagavi, Tumakuru, Davanagere, Shivamogga and every other district headquarters — accounts for only Rs 275 crore. Bengaluru is the problem.
The scale is the product of three forces that have been compounding since 2024. The Bengaluru Traffic Police accelerated the rollout of AI-enabled traffic junctions across the city, taking the network past 50 active intersections by 2025. These junctions use automatic number-plate recognition cameras tied to violation-detection software that flags signal jumps, helmet violations on two-wheelers, lane indiscipline, no-parking and dual-pillion offences. The cameras do not sleep, do not need a constable on duty, and do not give a verbal warning. Every flagged frame becomes a challan in the system, tagged to the registration number captured in the image.
The second force is the city's demographic churn. Bengaluru's IT-sector workforce changes employers and addresses more frequently than almost any other Indian metro. A vehicle bought in 2020 by an engineer working in Whitefield may have been driven by three different people on paper before being sold in 2024 to a buyer in Mysuru. The address on VAHAN is often the original purchase address, possibly an apartment the seller vacated years ago. SMS notifications to the registered mobile may bounce because the seller's number has changed. The result is a notification gap: the challan exists on the system, but no human is reading the notice.
The third force is collection velocity. The Bengaluru Traffic Police and the Karnataka State Police have offered intermittent settlement drives — including a discount push in 2024 — but these have not kept pace with issuance volume from the new AI infrastructure. Each month the system generates more challans than it disposes of, and the gap accumulates.
| Karnataka Challan Backlog | Figure | Buyer Implication |
|---|---|---|
| Bengaluru unpaid challans | Rs 1,425 crore | ~84% of state total |
| Karnataka state total | Rs 1,700 crore | 3.25 crore-plus violations |
| Active AI junctions | 50+ | 24x7 ANPR enforcement |
| Helmet / pillion fine | Rs 500 typical | Highest-volume violation |
| Signal jump fine | Up to Rs 2,500 | AI-flagged, no warning |
| Typical accumulated dues per car | Rs 15,000 - Rs 60,000 | Range varies by use pattern |
The IT-Sector Resale Loop
The Bengaluru resale market does not look like Mumbai's or Delhi's. A large share of supply comes from one specific pattern: salaried IT-sector employees who bought a car during a Bengaluru posting, accumulated routine fines from the city's AI junctions during three to five years of daily commuting, then took a job in Hyderabad, Pune, Singapore or the United States and decided to liquidate the car on the way out. The car is listed for sale on classifieds or sold quickly through a dealer network, the seller hands over keys and RC, leaves the city, and disappears from the buyer's reach within weeks.
Once the seller has moved, the buyer is alone with the registration number. If the original owner never updated their mobile in VAHAN, every challan notice goes to a dead phone. If the address was a rented apartment in Whitefield, every postal notice goes to whoever the landlord rented to next. The challans accumulate, escalate to Virtual Court status at the 60-day mark, and finally to physical court summons at the 90-day mark — all addressed to a registration number now legally held by someone who has never been to that junction.
The downstream effect lands in tier-two Karnataka. Bengaluru-registered used cars are routinely resold to buyers in Mysuru, Mangalore, Hubli-Dharwad and Belagavi at price points that look attractive on paper. A buyer in Mysuru picking up a Bengaluru-plate hatchback at a discount has every reason to feel pleased — until they try to register the vehicle in their name at the Mysuru RTO. The originating Bengaluru RTO will hold the Form 28 NOC until challans are settled. The transfer file stalls, the buyer either pays the dues to free the vehicle or sits with a car they cannot legally re-register, and the seller is already in another city or country.
Similar patterns play out for buyers in Mangalore and Hubli-Dharwad, both of which see steady inflow of Bengaluru-registered used cars. The cost of the surprise challan settlement, when it eventually surfaces at the RTO counter, almost always wipes out the price advantage the buyer thought they had captured at purchase.
How Karnataka RTO Handles RC Transfer with Pending Challans
The mechanics of the freeze are spelled out in Karnataka Motor Vehicles Rules and are now fully automated through the integrated Sarathi-VAHAN-Parivahan flow. Three forms drive a sale-to-registration transfer in Karnataka. Form 28 is the No Objection Certificate required when the vehicle is moving to another RTO or state. Form 29 is the notice of transfer of ownership filed by the seller. Form 30 is the buyer's application for entry of transfer in their name.
Each of these forms triggers backend queries against the central challan database, the road tax ledger and the hypothecation register. The system will not advance the file if any of three flags trip: pending challans against the registration number, unpaid road tax for the current cycle, or an active hypothecation entry that has not been closed by the financier. The check is automatic and the front-counter clerk has no discretion to override it.
In practice the buyer learns about the freeze after they have already paid the seller, taken delivery, often paid an agent or service provider to lodge the transfer, and shown up at the RTO expecting the new RC to be processed in three to four weeks. Instead they get a portal message or a counter intimation that the file is held because of pending dues. The seller is reachable for a few days, then increasingly difficult, then unreachable. The buyer either pays the dues themselves at echallan.parivahan.gov.in or the KSP portal — or accepts that the car will sit unregistered.
Road tax compounds the challan problem: Karnataka's lifetime road tax for cars is collected upfront at first registration but inter-state transfers and certain commercial-to-private re-registrations can leave gaps. The RTO transfer flow checks the tax ledger alongside the challan ledger. A buyer who has cleared challans but inherited a road-tax shortfall is still stuck at the same counter.
Who Pays — Buyer or Seller
The legal answer is straightforward in theory and uncomfortable in practice. Section 2(30) of the Motor Vehicles Act 1988 defines the registered owner as the person in whose name the vehicle is registered, and the seller remains the registered owner until the transfer is recorded in the buyer's name. So technically the seller is the registered owner at the moment the challan was issued, and the seller is legally liable for it.
In administrative practice that legal answer rarely helps the buyer. The Bengaluru Traffic Police is enforcing against the registration number, not against an individual. The RTO is freezing the transfer file against the registration number, not against the seller. When the buyer needs the car to be legally drivable in their name, the practical path is to pay the challans themselves and pursue the seller for reimbursement later. That recovery, against a seller who has changed cities, jobs and phone numbers, is a civil-court journey almost no one takes for amounts under Rs 50,000.
The companion piece on buyer-seller responsibility for pending challans walks through the legal distinction in more detail, and the article on whether old challans transfer to the buyer covers the Section 2(30) liability question with examples. The single takeaway: the only protection is to know before you pay, not to argue after.
Why DIY Checks Miss Karnataka Challans
The official lookup options for Karnataka challans are real but each has gaps that bite at the moment of a purchase decision. Pulling the registration through a Rs 49 Vahan Verify lookup returns every Bengaluru Traffic Police camera fine, every signal-jump challan and every helmet violation tagged to that RC in about 30 seconds, alongside the road tax status and hypothecation flag — but it is worth understanding why the free DIY routes are so often incomplete.
The Karnataka State Police e-Challan portal at the karnatakaone gateway is the official state lookup. It is the primary destination for Bengaluru-issued AI-junction challans, but the portal regularly runs slow, times out during peak hours, and occasionally returns partial lists because of sync delays with the AI junction backend. The Parivahan national e-challan portal at echallan.parivahan.gov.in covers most states but, in our testing, frequently lags KSP-issued data by hours to days. The VAHAN app and mParivahan require account login and only surface partial records linked to the logged-in user's phone or RC — not adequate for a buyer checking a stranger's registration. The VahanBazaar DIY check tip walks through these portals step by step.
| Lookup Route | Completeness | Data Freshness | Time to Result |
|---|---|---|---|
| KSP e-Challan portal | Bengaluru-only, often partial | Lag during peak load | 2 - 10 min if portal is up |
| Parivahan e-challan | National view, KSP sync lags | Hours to days behind KSP | 1 - 3 min |
| mParivahan app | Partial, login required | Same as Parivahan | 1 - 2 min after login |
| Vahan Verify (Rs 49) | VAHAN-consolidated, full record | Real-time API | ~30 seconds |
The portal-hopping trap: A buyer who relies only on the KSP portal can clear what they see, complete the deal, and still be caught by AI-junction challans that synced to the database 24 hours later. A buyer who relies only on Parivahan can miss KSP-issued violations that have not yet propagated. The risk is concentrated in exactly the Bengaluru cars buyers most want to verify — the ones with heavy AI-junction exposure.
Bengaluru Pre-Purchase: Verify the RC for Rs 49
Vahan Verify pulls the consolidated VAHAN record on any registration number — every pending challan, road tax due, fitness certificate, insurance status, owner serial and active loan flag. The same fields the RTO checks during transfer, returned to you in 30 seconds, before you hand over a single rupee.
What This Means for Used Car Buyers and Sellers
If you are buying any Bengaluru-registered used car — whether you are shopping in the city itself or considering a vehicle that has migrated to Mysuru, Mangalore, Hubli-Dharwad or Belagavi — treat the challan check as a non-negotiable step before token money changes hands. The Rs 1,425 crore figure is not abstract: it is the visible signal that a meaningful fraction of Bengaluru-plate cars currently on the market are carrying dues their sellers have either forgotten about or chosen not to mention.
- Pull a Vahan Verify before token: Before any money moves, run the registration through Vahan Verify. Thirty seconds, Rs 49, and you get every pending challan, road tax status, fitness flag, insurance entry and the hypothecation register entry in one consolidated VAHAN response. This is the same field set the RTO checks at the transfer counter, so if the report is clean, your transfer will not freeze for these reasons. If the report shows dues, you have priced information to negotiate with — and you have it before you are committed.
- Compare against the KSP portal: As a free cross-check, also pull the KSP e-Challan portal lookup for the same registration. It will sometimes show items still propagating from the AI junctions that even the VAHAN database will catch on the next sync. The two together give you the most complete picture available outside the RTO itself.
- Insist on clearance before final payment: If any pending challans surface, the simplest deal structure is to deduct the exact amount from the agreed price and clear the dues yourself at echallan.parivahan.gov.in or the KSP portal before completing the transfer. Take a timestamped receipt screenshot. Never accept "I will clear it later" — the seller's incentive to follow through evaporates the moment the keys change hands.
- Verify FASTag and toll history: Ask the seller to show the active FASTag account and confirm the linked Vehicle Registration Number matches the current RC. Bengaluru cars driven on the Bengaluru-Mysuru Expressway, the Tumakuru highway and the Hosur road accumulate FASTag transactions that can turn into mismatch challans if the tag was not updated through a previous ownership change.
- Check road tax separately: Karnataka's lifetime tax structure usually clears at first registration but inter-state imports and certain re-registrations can leave gaps. The Vahan Verify report shows the tax status field — confirm it reads paid for the current cycle before signing the sale agreement.
- Confirm hypothecation closure: If the car was purchased on loan, the original lender must have filed a Form 35 hypothecation termination at the RTO. The Vahan Verify report flags any open hypothecation entry. If one is still active, the RTO will freeze your transfer until the seller produces the NOC from their bank or financier.
- For inter-state moves, plan for NOC delay: If you are buying a Bengaluru-plate car for use in another state, budget time and money for the Bengaluru RTO to issue the Form 28 NOC. Any pending challan, tax due or hypothecation flag will block the NOC. Run Vahan Verify first, settle every flag, and only then start the NOC process.
The Bengaluru-specific rule of thumb: If the car has been registered in Karnataka for more than two years and has clocked daily commuting kilometres, assume there is at least one pending AI-junction challan on the RC. The probability that the seller knows about it is lower than you would expect — many AI-junction notices simply never reach the registered phone or address. The thirty seconds it takes to run a Vahan Verify lookup turns that uncertainty into a clean number you can negotiate against.
Buying a Bengaluru-Registered Used Car?
Bengaluru owes Rs 1,425 crore in unpaid traffic challans and the Karnataka RTO will freeze your RC transfer until every fine, tax due and hypothecation entry on the registration is cleared. Run Vahan Verify before token money changes hands.
Frequently Asked Questions
Bengaluru's Rs 1,425 crore backlog is the result of three forces compounding since 2024. First, the Bengaluru Traffic Police rolled out more than 50 AI-enabled junctions that capture signal jumps, helmet violations, lane indiscipline and no-parking offences 24 hours a day with no physical officer required. Second, the city's IT-sector workforce changes jobs and cities frequently, leaving outdated registered addresses on VAHAN so challan notices never reach the actual driver. Third, the city's challan settlement rate has lagged behind issuance volume, leading to a pile-up of more than 3.25 crore uncleared violations across Karnataka, of which Bengaluru contributes the overwhelming share.
Under Section 2(30) of the Motor Vehicles Act 1988 the registered owner remains liable until the RC transfer is completed in the new buyer's name. In practice, however, the administrative consequence sits on the person who actually has the car. The Karnataka RTO will block the Form 28, 29 and 30 transfer until every pending Bengaluru Traffic Police challan against the registration number is cleared. The buyer who has already taken physical delivery is the person who ends up paying — either by clearing the dues themselves or by chasing a seller who has, often, left the city. The only protection is to check and clear all challans before any money moves. See our companion piece on buyer-seller responsibility for the full breakdown.
Four practical options exist. The Karnataka State Police e-Challan portal is the official lookup but is frequently slow and incomplete for AI-junction fines. The national Parivahan e-challan portal covers most states but does not always reflect KSP-issued challans in real time. The VAHAN and mParivahan apps require login and only show partial records. The cleanest pre-purchase option is a paid lookup — VahanBazaar's Vahan Verify uses the VAHAN database to return every pending challan, fitness, insurance, road tax and hypothecation flag tagged to the registration in roughly 30 seconds for Rs 49.
No. Under Karnataka Motor Vehicles Rules, the Form 28 NOC, Form 29 notice of transfer and Form 30 application for transfer of ownership all trigger an automatic challan, road tax and hypothecation check against the registration number. If pending challans exist — whether issued by Bengaluru Traffic Police, Mysuru, Mangalore or any other Karnataka police unit — the RTO will hold the transfer file until receipts are produced. Inter-state cases are worse: the originating RTO will not issue the NOC for transfer to another state until the challan ledger is clean. See our explainer on how pending challans block RC transfer for the full process.
It is a starting point, not a complete picture. The KSP portal often misses recent AI-junction challans that have not yet synced into the public lookup, may not display Parivahan-routed CCTV challans from outside the city, and offers no view of road tax dues, NOC status or hypothecation entries that the RTO will check during transfer. A buyer relying only on the KSP portal can be caught out at the registration counter weeks after taking delivery. A single Vahan Verify lookup pulls the consolidated VAHAN record covering challans, road tax, fitness, insurance and the active loan flag, which is the same set of fields the RTO checks during transfer.