Everything, asked plainly.

Farleda helps you plan rail journeys across Europe and compare connections and estimated emissions with documented sources and assumptions.

Use the beta entry on this website. Before release it leads to the email signup; after release it opens the app. The free consumer beta is planned for 31 October–31 December 2026.

Rail, coach, ferry, car, walking and cycling as travel options, plus flights as the reference case a journey is compared against. Every mode carries its own factor, its own activity unit and its own honest range — they are listed on the methodology page.

Bookings take place with the transport provider. Where available, Farleda links to a booking service; check dates, fares and availability there. Results follow your chosen planning priority, such as emissions, journey time or fewer changes. Commission does not determine the order.

You can enable Klimaticket context in the settings. The current interface approximates coverage when both endpoints are in Austria; it does not yet verify service-level tariff validity or every operator's conditions. Always confirm the actual ticket rules before you travel.

No. You can simply use Farleda to compare connections, transfers and travel time. The emissions estimate is additional information for your decision.

Distance comes from schedule-feed geometry, road routing, or an explicitly labelled airport great-circle fallback. That distance is multiplied by a published factor per mode — the UK DESNZ tables as disclosed planning proxies, plus Farleda's grid model for electric rail. The activity unit, the range and the source are shown per leg.

Never. A language model is only ever used to write optional narrative text about a trip, and it can be switched off entirely. The emissions pipeline is deterministic: identical inputs, source values, factors and calculation rules give the same result. New timetable or electricity data can change a later calculation; the methodology version alone does not freeze every upstream source.

Occupancy, vehicle, energy source and operating conditions affect the result. Farleda’s ranges show plausible model scenarios, not measurements or statistical confidence intervals. Occupancy on a particular train is not measured.

Yes — flight factors include the DESNZ radiative-forcing uplift. Separate well-to-tank rows in the source workbook are not currently added on top, and that limitation is stated on the methodology page rather than buried.

From a published annual country snapshot of grid carbon intensity, converted to rail intensity with a stated modelling assumption of 0.09 kWh per passenger-kilometre. It is a product assumption, not a measurement of your specific train — the grid page publishes both the numbers and the limits of the model.

The methodology, source inventory and grid table can be read on this website. The public data API is planned for beta and released separately. The developer page explains its documented scope and current access.

A signed calculation record for a planned journey. It does not prove completed travel or avoided emissions and is not a carbon credit.

Once the public API is released, a Passport can be checked through Farleda without an application account. The verification page shows whether the service is active. The announced beta date does not automatically release the API.

The server signs a canonical payload with HMAC-SHA256 together with the declared methodology version. The public verifier checks format, signature and payload consistency, and a valid result shows that nothing has changed since Farleda signed it.

HMAC verification uses a shared server-side secret and is operated by Farleda. It checks calculation-record integrity but is not an independently verifiable public-key signature or confirmation of travel.

No. A saved plan or marked-complete trip is not operator-confirmed evidence of travel. The current Passport remains a signed calculation record.

No. It documents an estimate and a modelled comparison. It neither offsets emissions nor establishes causally avoided emissions.

On this website we store the information you submit for updates, inquiries or applications. A later app account also involves login/session data, saved journeys and preferences. Journey and event details can be personal data even without a user-ID field. Our privacy notice explains the website processing; app-specific notices are provided before account activation.

The information website uses no advertising pixels or external analytics SDKs. A session-storage preference remembers whether you have seen the brand introduction in this tab. Forms send data only when submitted. The separate app uses necessary login/session cookies.

Services receive data according to their purpose: for example coordinates, place names or an email address for delivery. Travel details and technical identifiers can also be personal data. The subprocessors and privacy pages explain the intended providers and processing; optional services depend on the release configuration.

Use the account deletion function when available in the released app, or contact the team through the privacy page. Account data, shared Passports, safety reports and backups have different retention requirements. The privacy notice explains the applicable process and exceptions.

A Passport is not automatically anonymous. Journey titles, routes and times can reveal personal information, even without an account name. Check the contents before sharing. The signature checks the calculation record, not the traveller’s identity.

A twelve-week pilot investigates one corridor, station cluster or data use case. Scope, deliverables, acceptance criteria, responsibilities and price are agreed in writing before work begins.

Data roles and any required processing agreement are settled before affected data is exchanged. The agreements reflect the actual pilot scope.

Not currently. The security page describes implemented controls, pending operational checks and known limits. We clarify mandatory certification or audit requirements before a pilot agreement.

Price and effort depend on the corridor, data access, integration scope and acceptance criteria. After joint scoping, you receive a written offer for the twelve-week pilot.

We are seeking the first railway and infrastructure partners. Published sample reports use synthetic reference cases, not demonstrated customer results.

There is no automatic licence commitment. Export, deletion, prototype access and the duration of verification are set out in the individual pilot agreement.

Try the consumer beta from 31 October to 31 December 2026 without payment details. There is no automatic paid renewal. Partner pilots are separate, paid projects.

We will explain continued access and any paid offers before the beta ends. Nothing turns into a paid subscription automatically.

No. Features, final price and release timing are still being developed. No payment details are requested for the consumer beta.

Stoicera Group currently covers operating costs. Paid pilots and licences, followed by possible traveller offers, are planned revenue sources. Grants, booking commissions and voluntary contributions are not secured income; commission is not intended to determine route ranking.

The free consumer beta is planned for 31 October–31 December 2026. The entry link follows the app’s release state; production use is targeted for early 2027, subject to readiness.