Corrections and error reports

CostMyTrip is a planning tool, and its pages contain estimates and catalogue data that can be wrong or go out of date. If you find a mistake, please tell us.

Report an error

Email contact@costmytrip.in with:

• the page address (route guides link here with the page filled in) or the trip you planned;
• what is wrong and what you believe is correct;
• your evidence — for example a link to an official notice, a toll receipt or NHAI TIS page, a timetable, or the date you travelled and what you saw;
• whether we may mention that a reader reported it (we never publish your email address).

Partner listings: use the “Report this listing” link on the card, or include the listing reference. Tell us what was wrong (for example a price, inclusion or policy that differed from the listing, or a problem with the operator). We may pause a listing while we check.

How we handle reports

• Reports are checked against the evidence provided and, where possible, an official or primary source.
• If a calculation, safety-related statement or source claim was wrong, we fix the page or data file in the next release and add an entry below.
• Small fixes that do not change meaning (typos, broken links, layout) are not listed.
• Calculator assumptions are changed only with a documented reason; a change that alters estimates is listed here with what changed.

How pages are produced

Route guides are generated from CostMyTrip's data files (the distance table, place catalogue, routing snapshots and the calculator) using page templates, with AI-assisted drafting. Some local notes on individual pages were written or edited by hand. Automatically generated sections — distances, times, costs, road references, nearby towns and suggested stops — are not individually reviewed. A page or section will say when it has been reviewed and on what date; if it does not say so, treat it as unreviewed.

Corrections history

Material corrections in releases prepared in October 2026. The site owner should record the publication date of each release when it goes live.

• Release v59 — Distance table: seven Kashmir pairs were added (Srinagar–Gulmarg 51 km, Srinagar–Pahalgam 98 km, Srinagar–Sonamarg 78 km, Jammu–Srinagar 237 km, Gulmarg–Pahalgam 149 km, Pahalgam–Sonamarg 173 km, Gulmarg–Sonamarg 120 km), from OSRM routing snapshots checked 8 Oct 2026, and Gulmarg, Pahalgam and Sonamarg are now treated as mountain terrain. Planner trips that include these pairs or places now use these distances and mountain speeds, mileage and toll factors; for example Pahalgam–Sonamarg was previously estimated from a straight line at about 39 km. No other trips change.
• Release v59 — Route guides: the suggested day plan no longer says “break near” a town that is more than about 6 km off the mapped road; it now says “take a break on the way” (23 pages, for example Kochi–Munnar and Delhi–Dehradun).
• Release v58 — Hyderabad–Srisailam: forest-road timings are now presented as reference guidance from dated news reports, not verified current access information; an unsupported “rechecked” date was removed; unverified third-party toll plazas and a ₹75–₹105 figure were removed in favour of the labelled calculator allowance.
• Release v58 — Route guides: “via” is now used only for towns within about 6 km of the mapped road (for example, Kochi–Munnar and Alleppey–Munnar no longer say “via Idukki”; Hyderabad–Vijayawada no longer says the road goes through Nalgonda). Terrain wording now separates the calculator's terrain setting from the real road.
• Release v58 — Planner: “Likely range / most likely” renamed “Planning range / base estimate” with the fixed percentages disclosed; numbers unchanged. Suggested stops are labelled as regional suggestions; “Passes through [states]” changed to “Selected places are in…”.
• Release v58 — Privacy: “Open in planner” links on route guides now carry the trip after # instead of in the query string, matching the Privacy Policy; the policy now explains older links, link contents and weather requests.
• Release v58 — Planner: a route-page fuel price carried into the planner was labelled “your input”; it is now labelled as the route page's indicative estimate unless you edited it. The value itself is unchanged.
• Release v56 — Travel times: the assumed average car speed was raised from 52 to 60 km/h (van and cab 48 to 55) and the rest/traffic allowances were revised, so drive-time estimates are shorter (for example Hyderabad–Tirupati 11.8–14.5 h became 9.5–11.7 h). Costs were not affected.