Transport Fever 3 Vehicles: A Practical Selection and Fleet-Sizing Guide | TF3 Field Guide

FIELD NOTES / 18 / English guide
Use a Transport Fever 3 vehicle list wisely: compare compatibility, capacity, real journey times, costs, and the number of vehicles a line actually needs.
Three practical questions to start with
Source-based guidance; not individually playtested. Official illustrations are credited to their authors. Compare the linked sources with your build and mods.
A vehicle purchase is a promise to pay for repeated journeys. Before comparing top speeds, decide what those journeys must accomplish: carry people from homes to destinations, deliver a specific cargo to a consumer, or move a reliable flow between two transfer points.
This guide explains how to read a Transport Fever 3 vehicle list and turn it into a purchase decision. It is a practical selection guide, with links to rosters for model lookup; it is not a copied database of every vehicle or a claim that one model wins on every map.
The most relevant list is the purchase screen in your own world. Its available vehicles reflect the conditions you are playing under and the content your setup actually contains. Start there, then use an external roster to compare the candidates you can buy.
The community vehicle directory provides another way to browse models. Check the directory's date, filters, and distinction between base-game and additional content before treating it as authoritative for your save. A catalog entry is a reference; the current in-game purchase information remains the final check.
The official vehicle manual explains vehicle categories and properties. The page we reviewed is marked as an old revision and includes Transport Fever 2 wording and legacy tables, so we do not present those tables as a verified TF3 launch roster. This is why this guide uses comparison methods and hypothetical calculations rather than copying old availability years or prices.
This is a planning sequence, not a fixed rule that road transport must always come first. On a particular map, waterways or an existing corridor may offer a better solution. Compare the complete service you would have to build, including the access lines at both ends.
An incompatible vehicle cannot compensate for good infrastructure. A cargo name in an industry panel must match something the intended vehicle can carry. For trains, inspect the wagons as well as the locomotive: propulsion and cargo capacity are different jobs.
Availability and compatibility come first. Confirm that the candidate exists in your world, carries the intended passengers or cargo, and can use the line's infrastructure. A roster entry outside your current availability conditions is not a purchase option.
Capacity comes next. Ask how much demand is waiting between departures. Carrying twice as much per trip may help a busy line; it may also leave a quiet line paying for empty space.
Actual journey time matters more than headline speed. Measure a representative return cycle, including intermediate stops, loading, junction delays, and traffic. A faster vehicle only earns an advantage if the route lets it use that speed.
Acceleration and traction affect that journey. Short urban sections repeatedly accelerate from stops. Heavy trains climbing grades ask a different question. Use the current purchase information and a test run instead of assuming two vehicles with the same top speed perform alike.
Purchase cost and operating cost need separate attention. One determines what you must spend now; the other determines the recurring burden after the service begins. Include the station and corridor investment when comparing a road option with a new railway.
Terminal and consist limits finish the check. A large vehicle or long train may require changes at several stops. Verify every destination, not just the depot from which you buy it.
Use a measured cycle and a clearly stated time unit. Imagine a demonstration line where one truck carries 20 units and takes 10 minutes to return to the same pickup point. If every outbound trip is full and every return is empty, its ideal outbound capacity is:
20 units ÷ 10 minutes = 2 units per minute.
A target of 5 units per minute would suggest at least three such trucks under those assumptions. Two provide an ideal 4; three provide an ideal 6. This is arithmetic for an illustrative route, not a TF3 vehicle specification or an annual production conversion.
The real line can deliver less because vehicles wait, load partially, bunch together, or share a congested terminal. Conversely, a valid loaded return journey changes the service's useful output. State which direction you are counting before comparing results.
For evenly spaced vehicles, the average interval is roughly the cycle time divided by fleet size. Three vehicles on a ten-minute cycle suggest about 3.3 minutes between departures, before bunching and delays. If they leave together, passengers or cargo will not experience that interval consistently.
Do not multiply a real-time estimate into “per game year” without checking the simulation clock and the calculator's assumptions. The tools guide explains what to record before using a line planner.
Prepare the line before buying a test vehicle. Check all stops, the path between them, and the vehicle's access from its depot. A purchase cannot repair a disconnected line.
Run the candidate through several representative cycles. Note departure load, arrival load, observed cycle time, terminal waiting, and the expense information shown for the service. For a passenger line, look at who boards at each stop; for cargo, confirm actual delivery to the intended recipient.
Then ask what limits the line. If people remain after every bus leaves full, capacity may be the problem. If buses run empty, investigate destination access and service quality. If a train spends half its cycle waiting at a junction, improving that junction may do more than buying a faster locomotive.
A useful replacement has a measurable goal: reduce crowding, carry a newly required carg