Line income estimator · observed cargo payment · passenger revenue · trip income
Transport Fever 3 income estimator
Anchor a revenue scenario to a payment from your own route. The Transport Fever 3 income estimator converts that observation into per-unit and per-trip revenue before scaling to your planned fleet.
Your scenario
Example values are illustrative. Replace them with observations from your save. Inputs stay in your browser.
Your planning result
Estimated revenue in the selected period
Revenue is scaled from your observed unit payment.
- Observed payment per unit
- 400 money / unit
- Average loaded units per delivery
- 32 units
- Revenue per vehicle delivery
- 12,800 money
- Completed fleet deliveries
- 48 deliveries
- Total units transported
- 1,536 units
- Revenue for one delivery by every vehicle
- 51,200 money
Calculation method & limits
Observed unit payment = observed delivery revenue ÷ delivered units. Average units per trip = vehicle capacity × load factor. Scenario revenue = unit payment × units per trip × vehicles × completed deliveries per vehicle. Keep the same route, cargo, economy settings and period. This is observation-based scaling, not a TF2 payment formula or a prediction of a different-distance route.
Calibrate a scenario with the Transport Fever 3 income estimator
A Transport Fever 3 income estimator is more useful when its starting point is a real payment. Enter the revenue and units from a completed delivery on the route you want to evaluate. The calculator derives a unit payment and scales it by expected loading and completed deliveries. It works for cargo or passengers when the observation and planned service use the same basis. Keep difficulty, distance, economy settings and cargo type unchanged when interpreting the estimate. A measurement from a different route is a separate scenario rather than a verified conversion rule.
How to use this Transport Fever 3 calculator
- Read one completed delivery payment and the number of units that actually earned it. Enter gross transport revenue, not a finance-panel net balance after operating expenses. The income estimator divides payment by those delivered units.
- Enter the planned vehicle capacity, achievable load factor and fleet size. Count revenue-producing deliveries per vehicle during one stated period; do not count an empty return as another paid delivery.
- Compare the Transport Fever 3 income estimator result with later receipts from the same route. Transfer the resulting period revenue to the route profit calculator and add costs on that same period basis.
A worked planning example
An observed delivery earns 12000 for 30 units, giving 400 per unit. A 40-unit vehicle loaded to 80% averages 32 units and 12800 per paid delivery. Four vehicles completing 12 paid deliveries each give 48 deliveries and estimated period revenue of 614400. Change loading to 50% and the revenue scenario falls to 384000. These demonstration figures are assumptions you can replace, not preset TF3 tariffs.
What to do with the result
Gross revenue is not profit. The income estimator leaves vehicle running cost, stations and other recurring expenses for the profit calculator. A faster timetable may increase deliveries, but station queues and cargo availability can prevent the planned trip count. Use the line planner and station calculator to cross-check that count. Re-measure the observed unit payment when changing the underlying route or economy, and compare estimates with actual receipts rather than assuming a universal Transport Fever 3 income formula.
Calculator questions
Does this Transport Fever 3 income estimator use the TF2 payment formula?
No. It derives unit revenue from your own delivery payment. It does not apply vehicle-speed coefficients or extrapolate another game's distance formula to TF3.
Can the income estimator calculate a completely different route?
Only as an explicitly hypothetical scenario using the entered payment. For a supported estimate, observe the route you plan to scale. Different distances, cargo and settings can change what one unit earns.
