BIZTRAC BETA
Freight transport by road

M.O. TRANSPORT AS

Org. no. 988942049 Limited company (AS) Lyngdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 16.9m
Operating profit NOK 1.4m
Equity NOK 1.1m
Incorporated 2005
Employees 24
Share capital NOK 100,000

M.O. TRANSPORT AS is registered as a limited company in Lyngdal, Agder with organisation number 988942049. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2005 and has 24 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Avisdistribusjon, transport med varebiler samt annen transportvirksomhet, handel, erverv og drift av eiendommer samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 16.9m
Operating profit
NOK 1.4m
Equity
NOK 1.1m
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns M.O. TRANSPORT AS?

STJERNA AS
M.O. TRANSPORT AS
NOK 16.9m rev. · NOK 1.4m profit

M.O. TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M.O. TRANSPORT AS

Who owns M.O. TRANSPORT AS?

STJERNA AS is the largest registered owner, with 100.0%.

What is the revenue of M.O. TRANSPORT AS?

M.O. TRANSPORT AS had revenue of NOK 16.9m in 2024.

Who is the general manager of M.O. TRANSPORT AS?

Joakim Hellestøl is registered as general manager of M.O. TRANSPORT AS.

Where is M.O. TRANSPORT AS based?

M.O. TRANSPORT AS has its business address in Lyngdal.

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.