BIZTRAC BETA
Service activities incidental to water transportation

NORSK BERGING AS

Org. no. 922653062 Limited company (AS) Bømlo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 201,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORSK BERGING AS is registered as a limited company in Bømlo, Vestland with organisation number 922653062. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Berging og sjørelatert virksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 201,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 201,000
Equity
NOK 1.5m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns NORSK BERGING AS?

B-M INVEST AS
NORSK BERGING AS
NOK 3.3m rev. · NOK 201,000 profit

NORSK BERGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK BERGING AS

Who owns NORSK BERGING AS?

B-M INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of NORSK BERGING AS?

NORSK BERGING AS had revenue of NOK 3.3m in 2024.

Who is the general manager of NORSK BERGING AS?

Lars Lønning is registered as general manager of NORSK BERGING AS.

Where is NORSK BERGING AS based?

NORSK BERGING AS has its business address in Bømlo.

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.