Compare Daily Tolls With the Budget You Set — Free
A toll that looks trivial per crossing adds up across a day of driving. Multiply crossings by the toll, compare each day with the budget you set, and keep the flagged day visible.
The proof surface
Road-trip leg splitters divide a route between days. This totals toll cost per driving day against a chosen daily budget, so an expensive motorway day is visible before the trip.
Why the flat version breaks
Multiplying one-way only
Most crossings happen in both directions.
Using last year’s tariff
Road tolls change, and vehicle classes change the price.
Treating the budget as a fee cap
The operator charges the published toll regardless of your budget.
How to work the toll day ledger
Enter today’s price for the vehicle class you will drive; tariffs change with season, class and payment method. The setting is your own daily budget, not a published figure.
A crossing usually happens twice if you come back. Four motorway crossings at four units each is 16 for that day, which is over the 12-unit budget in the sample.
Days above the budget are flagged. A flagged day is not a mistake; it is a day where a slower route, an off-peak crossing or a different payment card is worth checking.
Toll rules, discounts and unpaid-crossing penalties vary by operator and country. Check the official tariff and payment method, and never rely on this estimate to avoid a fine.
What the toll day ledger replaces
| Question | Before | Visible working |
|---|---|---|
| Multiplying one-way only | Most crossings happen in both directions. | Count both directions |
| Using last year’s tariff | Road tolls change, and vehicle classes change the price. | Read over-budget days as a routing prompt |
| Treating the budget as a fee cap | The operator charges the published toll regardless of your budget. | Confirm before you drive |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
FIRST-LOAD
Research prototype — checkout unavailable. Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
This is travel-cost arithmetic on prices you supply and is not a tariff quote or a payment guarantee. Confirm current tolls, classes and payment terms with the road operator before travelling.
Data note: Everything runs in this browser tab on the toll day ledger: your route day | toll units per crossing | crossings planned stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a clerk's docket sheet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the toll day ledger reading, and holds your drafts on this device — one complete free run; the proposed $4 one-time filing layer is not currently for sale.
The toll day ledger reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the compare daily tolls with the budget you set companionBoundary
This is travel-cost arithmetic on prices you supply and is not a tariff quote or a payment guarantee. Confirm current tolls, classes and payment terms with the road operator before travelling.
What this is built on
- Method: Days above the budget are flagged. A flagged day is not a mistake; it is a day where a slower route, an off-peak crossing or a different payment card is worth checking.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: Most crossings happen in both directions. After: the toll day ledger shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this toll day ledger, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a toll day ledger. Return plain rows only: route day | toll units per crossing | crossings planned. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: route day | toll units per crossing | crossings planned. No AI response is executed as code.