BIZTRAC BETA
Freight transport by road

HAMO TRANSPORT AS

Org. no. 982435285 Limited company (AS) Bærum Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1.0m
Equity NOK 596,000
Incorporated 2000
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,0 mill kr).

HAMO TRANSPORT AS is registered as a limited company in Bærum, Akershus with organisation number 982435285. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportvirksomhet og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1.0m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1.0m
Equity
NOK 596,000
Est. value
NOK 633,000

Financial health · 2025

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

Who owns HAMO TRANSPORT AS?

MORTEN STANGELAND
HAMO TRANSPORT AS
NOK 0 rev. · NOK −1.0m profit

HAMO TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAMO TRANSPORT AS own?

HAMO TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAMO TRANSPORT AS

Who owns HAMO TRANSPORT AS?

MORTEN STANGELAND is the largest registered owner, with 100.0%.

What is the revenue of HAMO TRANSPORT AS?

HAMO TRANSPORT AS had revenue of NOK 0 in 2025.

Who is the general manager of HAMO TRANSPORT AS?

Morten Stangeland is registered as general manager of HAMO TRANSPORT AS.

Where is HAMO TRANSPORT AS based?

HAMO TRANSPORT AS has its business address in Rud.

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.