Simutrans is a long-running, open-source transport simulation in which success comes from building a network rather than merely placing vehicles. The project remains actively maintained, and its July 2026 activity gives Linux players a timely reason to revisit it. It runs natively, costs nothing, and can scale from a quiet bus route to a dense system of trains, ships, trucks, trams, monorails, and aircraft.
This guide explains the safest installation choices, the first profitable route, and the settings that matter most on a modern Linux desktop. The official project site is [simutrans.com](https://www.simutrans.com/).
> Image note: the illustrations below are **stylised mockups — official screenshots unavailable** during publication research. They describe the concepts but are not captures of the game interface.
## What makes Simutrans different?
Many city builders treat transport as one service among many. Simutrans makes movement the whole economic puzzle. Industries produce goods, factories consume inputs, towns generate passengers and mail, and every shipment has a destination. You cannot profit by sending a vehicle aimlessly between convenient stops. A useful connection must join real demand to a reachable destination.
That destination-based model creates interesting consequences. A full station is not automatically healthy: cargo may be waiting for a destination your network cannot reach. Adding more vehicles may only increase congestion and maintenance. The correct fix might be a missing transfer, a larger platform, or a redesigned timetable.
Simutrans also separates its engine from “paksets.” A pakset supplies graphics, vehicles, buildings, industries, and balancing rules. Pak64 is compact and approachable; Pak128 offers larger artwork and a different economy. Saves depend on their pakset, so choose one and keep it installed.
## How to install Simutrans on Linux
### Use your distribution package
The repository build is usually the least surprising choice. On Debian or Ubuntu, try:
“`bash
sudo apt update
sudo apt install simutrans simutrans-pak64
“`
On Fedora, package availability can vary by release:
“`bash
sudo dnf install simutrans
“`
On Arch Linux:
“`bash
sudo pacman -S simutrans
“`
Launch it from the application menu or run `simutrans`. Distribution packages integrate well with desktop menus and updates, but may trail the newest upstream release. Check the version in the title screen or help dialog if a recent fix matters to you.
### Use Flatpak when available
Search Flathub rather than copying an unverified application ID:
“`bash
flatpak search Simutrans
“`
If a maintained result appears, install the exact ID shown by the search. Flatpak is useful when your distribution package is old, but verify where saves and paksets are stored before manually adding content. `flatpak info
### Use the official download
Upstream archives are valuable when you want a recent engine or pakset. Download only from the official site, extract the archive into a directory you own, and run the supplied executable. Do not move random game files into `/usr/bin`; keeping a self-contained folder under `~/Games` makes updates and rollback easier.
Before replacing a working version, back up your Simutrans user directory. Its exact location can differ by build and packaging format, so use the game’s directory information or inspect the package documentation rather than assuming one path.
## Start with a route that can work
Create a small map, use an easy economic setting, and pause immediately. Locate two nearby towns or an industry chain with obvious producer and consumer labels. Passenger service between neighboring towns is easier to understand, while a short freight chain teaches the industry model more clearly.
Place one stop in each town’s populated area. Stops have catchment zones; buildings outside the highlighted area will not contribute demand. Build the simplest direct road, add a depot connected to it, buy one or two suitable buses, assign both stops to a schedule, and start the convoy.
Do not buy ten vehicles before observing one. Let the route run for several months and inspect its finances. If vehicles travel mostly empty, check whether both stops are in useful catchment areas and whether passengers can actually reach desired destinations. If crowds grow continuously, add capacity gradually.
For freight, match every detail: the producing industry, the consuming industry, cargo type, station coverage, and vehicle capability. A truck that can carry “goods” cannot necessarily carry coal, oil, or grain. Open the industry information windows and follow the listed suppliers and consumers.
## Build transfers instead of spaghetti
As the network grows, organize it into lines. A line stores a shared schedule for multiple convoys, making later edits much safer. Build a high-capacity trunk between major towns and use buses or trams as feeders. This hub-and-spoke pattern is easier to expand than giving every origin a direct service to every destination.
Transfers need enough station capacity and sensible timing. Extremely long waits reduce network usefulness. Conversely, excessive vehicle frequency wastes money and blocks roads. A practical goal is regular service with modest spare capacity, not a permanently empty platform.
Railways need careful geometry. Leave room for longer platforms, passing loops, and signals before development surrounds the corridor. Begin with a single train on a simple line. Add signalling only when you understand where trains must wait; complex track does not create capacity unless blocks and junctions are designed coherently.
## Read the financial signals
Separate route revenue from the company cash balance. A vehicle can earn fares while still losing money after running costs. Infrastructure maintenance can turn an apparently busy network into a deficit. Open convoy, line, and finance windows regularly.
When a route loses money, diagnose it in this order:
1. Confirm that a valid origin-destination demand exists.
2. Confirm that stops cover the relevant buildings or industries.
3. Confirm that the vehicle accepts the cargo.
4. Check load factors in both directions.
5. Reduce frequency or replace oversized vehicles.
6. Shorten wasteful detours and remove unused infrastructure.
Bidirectional demand is powerful. Passenger lines often carry riders both ways, while early freight routes may return empty. Combine compatible flows or choose compact chains to reduce unproductive mileage.
## Linux-specific practical tips
If the interface is tiny on a HiDPI monitor, inspect the display and GUI scaling options before forcing compositor-level scaling. Test windowed and fullscreen modes; behavior depends on the graphics backend, desktop environment, and package build.
Audio trouble is usually packaging-specific. First test whether other applications produce sound, then launch Simutrans from a terminal and look for missing-library messages. Avoid installing obsolete audio libraries from unknown repositories simply to silence a warning.
For backups, close the game before copying saves. Keep several dated generations rather than continuously overwriting one archive. If you use Steam Cloud, Syncthing, or another synchronizer, avoid opening the same save on two computers simultaneously.
Performance problems usually come from simulation scale, not graphics. Huge maps, many convoys, and complex pathfinding increase CPU load. Start modestly, use the fast-forward control sparingly on developed maps, and retire redundant vehicles. Native packages often perform well even on older integrated graphics.
## Updating without breaking a save
Back up saves and record the pakset name and version. Engine updates are often smooth, but pakset changes can alter economics or remove assets. Test an important save in a copied profile before committing. If an update causes trouble, keep the old executable and pakset together until migration is proven.
Never download a save dependency from an untrusted link merely because a dialog reports missing objects. Find the corresponding official pakset release. Mixing similarly named files from unrelated pakset versions is a common way to produce confusing warnings.
## A good first-hour plan
Spend the first ten minutes learning pause, map overlays, station catchment, and information windows. Use the next twenty to build one two-stop passenger line. Observe it for several in-game months, then add a feeder or a second vehicle only when the waiting count justifies it. Finally, attempt one short industry chain and compare its two-way utilization with the passenger route.
That measured approach reveals Simutrans’ core pleasure: every expansion is an engineering hypothesis. Build a connection, watch passengers and cargo choose paths, read the accounts, then improve the bottleneck. On Linux, the native and open-source foundation makes it an especially durable game—easy to preserve, lightweight to run, and deep enough to reward years of network redesign.
Comments