BIZTRAC BETA
Service activities incidental to water transportation

BJØRNEVIKA BÅDSENTER AS

Org. no. 927137453 Limited company (AS) Lillesand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.8m
Operating profit NOK 1.8m
Equity NOK 1.8m
Incorporated 2021
Employees 11
Share capital NOK 30,000

BJØRNEVIKA BÅDSENTER AS is registered as a limited company in Lillesand, Agder with organisation number 927137453. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2021 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive båtopplag, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.8m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 9.8m
Operating profit
NOK 1.8m
Equity
NOK 1.8m
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.3%
Satisfactory
Equity as a share of total capital

Who owns BJØRNEVIKA BÅDSENTER AS?

BÅDSENTER GRUPPEN AS
BJØRNEVIKA BÅDSENTER AS
NOK 9.8m rev. · NOK 1.8m profit

BJØRNEVIKA BÅDSENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRNEVIKA BÅDSENTER AS

Who owns BJØRNEVIKA BÅDSENTER AS?

BÅDSENTER GRUPPEN AS is the largest registered owner, with 50.0%.

What is the revenue of BJØRNEVIKA BÅDSENTER AS?

BJØRNEVIKA BÅDSENTER AS had revenue of NOK 9.8m in 2025.

Who is the general manager of BJØRNEVIKA BÅDSENTER AS?

Morten Aleksander Flesje is registered as general manager of BJØRNEVIKA BÅDSENTER AS.

Where is BJØRNEVIKA BÅDSENTER AS based?

BJØRNEVIKA BÅDSENTER AS has its business address in Høvåg.

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.