BIZTRAC BETA
Freight transport by road

BJØRN M. HAUG TRANSPORT AS

Org. no. 998820545 Limited company (AS) Moss Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 12.2m
Operating profit NOK 487,000
Equity NOK 1.0m
Incorporated 2012
Employees 8
Share capital NOK 100,000

BJØRN M. HAUG TRANSPORT AS is registered as a limited company in Moss, Østfold with organisation number 998820545. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Godstransport på vei, kjøring i Oslo og omegn og annen nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.2m in revenue and NOK 487,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.2m
Operating profit
NOK 487,000
Equity
NOK 1.0m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BJØRN M. HAUG TRANSPORT AS?

BJØRN MARTIN HAUG
BJØRN M. HAUG TRANSPORT AS
NOK 12.2m rev. · NOK 487,000 profit

BJØRN M. HAUG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRN M. HAUG TRANSPORT AS

Who owns BJØRN M. HAUG TRANSPORT AS?

BJØRN MARTIN HAUG is the largest registered owner, with 100.0%.

What is the revenue of BJØRN M. HAUG TRANSPORT AS?

BJØRN M. HAUG TRANSPORT AS had revenue of NOK 12.2m in 2024.

Who is the general manager of BJØRN M. HAUG TRANSPORT AS?

Bjørn Martin Haug is registered as general manager of BJØRN M. HAUG TRANSPORT AS.

Where is BJØRN M. HAUG TRANSPORT AS based?

BJØRN M. HAUG TRANSPORT AS has its business address in Moss.

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.