Sisu Auto
Finnish vehicle manufacturer

Oy Sisu Auto Ab is a truck manufacturer based in Raseborg, Finland. Its name comes from the Finnish word sisu meaning guts, grit and determination.
Sisu Auto has a subsidiary company, Sisu Defence, producing high mobility tactical vehicles for military use.
Production
Civil trucks
The currently available Sisu Polar variants are with three, four or five axles in various layouts. The applications are:
Sisu Crane – crane trucks
Sisu Rock – dump trucks
Sisu Roll – hook loader
Sisu Timber – timber trucks
Sisu Works – road maintenance trucks
Sisu Carrier – heavy machinery carrier
Military trucks
Sisu 4×4
Sisu 6×6
Sisu 8×8
Sisu 10×10
History
1931 to 1939
The company was established on 1 April 1931 as Oy Suomen Autoteollisuus Ab (SAT). It originated from two neighbouring Helsinki-based automobile coach builders, Autokoritehdas and Autoteollisuus-Bilindustri, both of which had fallen into financial troubles by the beginning of the 1930s. The banks, which were funding both companies, pressed them to put together their operations under one company. The founders were Emil Anton Winckelmann, Lars Wilhelm Åberg and Karl Arthur Nordgren. In the first company meeting the company general manager was selected John Hellsten and the technical manager was appointed Tor Nessling.
At first SAT continued the coachbuilding business which it had inherited from its predecessors, but also put into practice the plan of building own vehicles, which was evolved already earlier, when Autoteollisuus-Bilindustri had ordered few Volvo chassis for outfitting.
This brief starts where responsible research should: with the source description of “Sisu Auto” as finnish vehicle manufacturer. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as finnish vehicle manufacturer. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jun 15, 2026. The linked authority identifier is Q1388470. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1931 and 1939.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Sisu Auto”, its source revision and the description used here.
- Expand the search: follow Sisu Auto primary sources, Sisu Auto archive and Sisu research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Sisu Auto”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Sisu Auto” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.