BIZTRAC BETA
Freight coastal transport

BRØNNBÅT NORD LOFOTEN AS

Org. no. 923107479 Limited company (AS) Ibestad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 61.6m
Operating profit NOK 14.0m
Equity NOK 89.9m
Incorporated 2019
Share capital NOK 1.1m

BRØNNBÅT NORD LOFOTEN AS is registered as a limited company in Ibestad, Troms with organisation number 923107479. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2019. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Å drive rederi virksomhet. Samt andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.6m in revenue and NOK 14.0m in operating profit.

Key figures · 2024

Revenue
NOK 61.6m
Operating profit
NOK 14.0m
Equity
NOK 89.9m
Est. value
NOK 81.1m

Financial health · 2024

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

Who owns BRØNNBÅT NORD LOFOTEN AS?

BRØNNBÅT NORD AS
BRØNNBÅT NORD LOFOTEN AS
NOK 61.6m rev. · NOK 14.0m profit

BRØNNBÅT NORD LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØNNBÅT NORD LOFOTEN AS

Who owns BRØNNBÅT NORD LOFOTEN AS?

BRØNNBÅT NORD AS is the largest registered owner, with 50.0%.

What is the revenue of BRØNNBÅT NORD LOFOTEN AS?

BRØNNBÅT NORD LOFOTEN AS had revenue of NOK 61.6m in 2024.

Who is the general manager of BRØNNBÅT NORD LOFOTEN AS?

Per Harald Olsen is registered as general manager of BRØNNBÅT NORD LOFOTEN AS.

Where is BRØNNBÅT NORD LOFOTEN AS based?

BRØNNBÅT NORD LOFOTEN AS has its business address in Engenes.

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.