biztrac. BETA
COMPANY REGISTER PROFILE
930153605 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LANGESUND BÅTHAVN AS

Org. no. 930153605 Limited company (AS) Bamble Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 37,000
Equity NOK 1.6m
Incorporated 2022
Employees 8
Share capital NOK 30,000

LANGESUND BÅTHAVN AS is registered as a limited company in Bamble, Telemark with organisation number 930153605. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av marina med småbåthavn.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
▼ −9 %
Operating profit
NOK 37,000
▼ −91 %
Equity
NOK 1.6m
▲ +2 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
1.0%
Weak
Return on total assets
Solidity
40.2%
Very good
Equity as a share of total capital

Who owns LANGESUND BÅTHAVN AS?

LANGESUND BÅTHAVN AS
NOK 5.5m rev. · NOK 37,000 profit

LANGESUND BÅTHAVN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGESUND BÅTHAVN AS

Who owns LANGESUND BÅTHAVN AS?

Andrei Bordeianu is the largest registered owner, with 100.0%.

What is the revenue of LANGESUND BÅTHAVN AS?

LANGESUND BÅTHAVN AS had revenue of NOK 5.5m in 2025.

Who is the general manager of LANGESUND BÅTHAVN AS?

Andrei Bordeianu is registered as general manager of LANGESUND BÅTHAVN AS.

Where is LANGESUND BÅTHAVN AS based?

LANGESUND BÅTHAVN AS has its business address in Langesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.