BIZTRAC BETA
Scheduled long distance passenger transport in coastal waters

BOLÆRNEBÅTENE AS

Org. no. 918422617 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −81,000
Equity NOK 447,000
Incorporated 2017
Employees 6
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).

BOLÆRNEBÅTENE AS is registered as a limited company in Bærum, Akershus with organisation number 918422617. The business is classified under scheduled long distance passenger transport in coastal waters (NACE 50.102). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 50,000, divided into 5000 shares. The company's stated purpose is: “Båttransport.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −81,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −81,000
Equity
NOK 447,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns BOLÆRNEBÅTENE AS?

HANS SKAAR
BOLÆRNEBÅTENE AS
NOK 1.7m rev. · NOK −81,000 profit

BOLÆRNEBÅTENE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BOLÆRNEBÅTENE AS er morselskap for 1 datterselskap:

Frequently asked questions about BOLÆRNEBÅTENE AS

Who owns BOLÆRNEBÅTENE AS?

HANS SKAAR is the largest registered owner, with 100.0%.

What is the revenue of BOLÆRNEBÅTENE AS?

BOLÆRNEBÅTENE AS had revenue of NOK 1.7m in 2024.

Who is the general manager of BOLÆRNEBÅTENE AS?

Hans Skaar is registered as general manager of BOLÆRNEBÅTENE AS.

Where is BOLÆRNEBÅTENE AS based?

BOLÆRNEBÅTENE AS has its business address in Høvik.

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.