BIZTRAC BETA
Business and other management consultancy activities

LAAGEN DAMPSKIBSSELSKAB AS

Org. no. 922747768 Limited company (AS) Kongsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 2.5m
Equity NOK 3.6m
Incorporated 2019
Share capital NOK 30,000

LAAGEN DAMPSKIBSSELSKAB AS is registered as a limited company in Kongsberg, Buskerud with organisation number 922747768. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering og forvaltning av kapital, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 2.5m
Equity
NOK 3.6m
Est. value
NOK 10.1m

Financial health · 2025

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

Who owns LAAGEN DAMPSKIBSSELSKAB AS?

MORTEN URDAL BAKKE
LAAGEN DAMPSKIBSSELSKAB AS
NOK 2.7m rev. · NOK 2.5m profit

LAAGEN DAMPSKIBSSELSKAB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAAGEN DAMPSKIBSSELSKAB AS own?

LAAGEN DAMPSKIBSSELSKAB AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about LAAGEN DAMPSKIBSSELSKAB AS

Who owns LAAGEN DAMPSKIBSSELSKAB AS?

MORTEN URDAL BAKKE is the largest registered owner, with 100.0%.

What is the revenue of LAAGEN DAMPSKIBSSELSKAB AS?

LAAGEN DAMPSKIBSSELSKAB AS had revenue of NOK 2.7m in 2025.

Where is LAAGEN DAMPSKIBSSELSKAB AS based?

LAAGEN DAMPSKIBSSELSKAB AS has its business address in Kongsberg.

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.