BIZTRAC BETA
Freight transport by road

STIG LOSEN TRANSPORT AS

Org. no. 993351679 Limited company (AS) Melhus Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 26.7m
Operating profit NOK 1.8m
Equity NOK 11.2m
Incorporated 2008
Employees 22
Share capital NOK 1.2m

STIG LOSEN TRANSPORT AS is registered as a limited company in Melhus, Trøndelag with organisation number 993351679. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2008 and has 22 registered employees. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Drive transport av gods og varer, samt handel av produkter som naturlig knytter seg til slik virksomhet. Selskapet skal også tilby verkstedtjenester for kjøretøy samt drifte dekkhotell inkludert kjøp og salg av dekk. Selskapet skal også kunne delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 26.7m
Operating profit
NOK 1.8m
Equity
NOK 11.2m
Est. value
NOK 12.9m

Financial health · 2025

Liquidity
2.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.3%
Very good
Equity as a share of total capital

Who owns STIG LOSEN TRANSPORT AS?

LOSEN HOLDING AS
STIG LOSEN TRANSPORT AS
NOK 26.7m rev. · NOK 1.8m profit

STIG LOSEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STIG LOSEN TRANSPORT AS

Who owns STIG LOSEN TRANSPORT AS?

LOSEN HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of STIG LOSEN TRANSPORT AS?

STIG LOSEN TRANSPORT AS had revenue of NOK 26.7m in 2025.

Where is STIG LOSEN TRANSPORT AS based?

STIG LOSEN TRANSPORT AS has its business address in Kvål.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.