EV Grids (evgrids.in) helps drivers plan long-distance trips in electric vehicles across India. We rank DC fast-charging stops along your actual driving route, estimate battery use and trip cost, and open turn-by-turn navigation in Google Maps. The product is a charging-stop planner, not a navigation app.
Who runs EV Grids — and why a driver built it
EV Grids is built and maintained by Raza Sikander, an EV driver who got tired of planning Hyderabad-side highway trips as a spreadsheet of brochure kilometres and random Google Maps pins. The first versions existed because a Nexon-class pack on NH44 does not behave like a full petrol tank, and because a highly rated charger in a city centre is often the wrong stop. The site is an independent project — we are not affiliated with, endorsed by, or operated on behalf of any automaker, charging network operator, or maps provider. Vehicle names and network brands on the site are used only to describe presets and public charging locations.
That driving experience is the editorial standard: corridor pages talk about stop belts, heat, ghats, and backups because those are the ways trips actually fail. We do not invent live queues, pole tariffs, or first-hand claims we did not record. Where a number is arithmetic (distance × Wh/km), we say so. Where something is general guidance, we say so. Dated trip reports, when published, are the only place we treat a kilometre or a rupee as measured on a specific day.
There is no outside newsroom and no call centre. Support is email and the in-site feedback form. Typical replies take a few business days. See contact.
What we publish
The homepage is the interactive planner. Around it we maintain educational pages that should stand alone if you never open the form: how EV Grids works, EV charging guide, range and SOC, trip cost calculator, and charger data & accuracy. Long-form road-trip articles live under guides. Named highways such as Hyderabad → Goa or Bangalore → Chennai have corridor pages with distance, typical stop strategy, and a Plan now button. Vehicle pages explain how a given model should be planned — connectors, highway Wh/km caveats, and suited corridors — not just a copy-pasted template.
The blog is reserved for dated notes (including occasional weekly corridor recaps). Draft posts stay unpublished. We do not use the blog as a doorway farm.
How the routing algorithm works (in plain language)
When you enter origin, destination, and a vehicle preset, the API asks Google Directions (or OpenRouteService when configured) for the driving polyline — the road, not a straight line. Fast chargers are discovered near sampled points on that path. Sites far from the drive are dropped even if they look close on a map. Each candidate is scored: detour from the polyline, power, ratings, operational status, amenities, a reliability prior from listing data, and optionally estimated ₹/kWh. The top reachable site at each SOC trigger becomes the primary; nearby alternatives become backups. Swapping a backup re-checks later legs so stop two cannot strand stop three.
State of charge is a walk along that polyline using your Wh/km, start SOC, search threshold, and reserve floor — not a live feed from the battery. With Wh/km left blank, certified range is planned at 0.80, and never below 120 Wh/km. A figure you type replaces that derate. Results may be cached so repeat city pairs stay fast. Then the itinerary opens in Google Maps with your selected chargers as waypoints. EV Grids does not navigate, book a stall, or start a session. The full pipeline, including the live ranking weights, is documented on how EV Grids works and in the methodology guide.
How charger information is handled
Listings combine cached public map data and live lookups. We do not promise a gun will be free. Indicative ₹/kWh is inferred or last-known when a live tariff is missing. If a pin is wrong, use contact or the footer Feedback form (wrong charger, dead charger, route, vehicle data, or content correction).
What we do not guarantee
Charger availability, pricing, and site access change daily. Outages, queues, and road closures happen. Always confirm a backup charger before you leave, and treat SOC estimates as planning aids — not a substitute for your car's display and your own margin. The accuracy policy is the charger data page.
Who writes this
Raza Sikander
Independent EV driver and the person who writes the corridor notes and routing docs. Hyderabad-side highway trips are the original test bed. There is no newsroom and no automaker retainer — vehicle names on the site are presets.
Privacy, ads, and accounts
See Privacy, Terms, and data safety. Some editorial pages show ads. Optional Google sign-in stores an account so you can sync trips; it does not grant admin access.
Editorial corrections
Send charger, route, vehicle, or article corrections through contact or the footer feedback form. Include the page, the station or corridor, and what you observed. We correct copy and presets when a report checks out, and we can flag a listing inside the planner. A report does not rewrite the operator’s own map, and it does not appear as a “data checked” date. We show a checked date only after a person has actually reviewed that page. Estimates — arrival SOC, charge time, ₹/kWh, and stop lists — stay labelled as estimates. Measured kilometres, kWh, or rupees appear only in a dated trip report that records them.
Contact
Questions, partnerships, or corrections: contact page or email raza.sikander.s@gmail.com.