VEYRA / DATA

Trust starts with clarity.

What comes from a source, what is calculated, and what remains unknown: we show the boundaries.

Station source

Data source: yonga.io. Yonga supplies station and charging-network metadata. Documentation describes daily updates and caching; this is not live connector occupancy. VEYRA’s production feed is enabled through an authorized server-side API connection.

Availability and pricing

The current source does not provide live connector occupancy. “Active” never means “available now”. Network AC, fast DC and ultra-fast DC tariffs are not verified connector prices. Unclear membership, time, tax or power-band conditions prevent a claim of exact cost.

Energy and routing

Apple MapKit supplies road distances and travel times. VEYRA adds a separate model using usable capacity, consumption, starting SOC and arrival reserve. Charging stops must pass reachability checks. Missing prices and unverified charging curves are stated in results.

Freshness and offline use

Source update time and VEYRA retrieval time are separate. The last successful records may be shown as labeled cache for up to 24 hours. New road routing and place searches require internet. Old records are not presented as current status.

Vehicle information

There is no vehicle connection or automatic SOC reading. Users confirm vehicle inputs. The BYD SEAL 2026 Türkiye template does not automatically fill usable capacity: the brochure’s published 82.5 kWh does not specify gross versus usable.

Official references

Yonga API · Yonga terms · Apple MapKit · BYD Türkiye · SEAL 2026