BIZTRAC BETA
COMPANY REGISTER PROFILE
993336777 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of sports clubs

LYSAKERFJORDEN BRETTSEILERKLUBB

Org. no. 993336777 Association/club/organisation (FLI) Bærum Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 165,000
Equity NOK 4.8m
Incorporated 1981

LYSAKERFJORDEN BRETTSEILERKLUBB is registered as a association/club/organisation in Bærum, Akershus with organisation number 993336777. The business is classified under activities of sports clubs (NACE 93.120). The company was incorporated in 1981. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 165,000
Equity
NOK 4.8m
Est. value
NOK 3.2m

Financial health · 2023

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

Who owns LYSAKERFJORDEN BRETTSEILERKLUBB?

No shareholders are registered for LYSAKERFJORDEN BRETTSEILERKLUBB in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LYSAKERFJORDEN BRETTSEILERKLUBB

What is the revenue of LYSAKERFJORDEN BRETTSEILERKLUBB?

LYSAKERFJORDEN BRETTSEILERKLUBB had revenue of NOK 1.6m in 2024.

Where is LYSAKERFJORDEN BRETTSEILERKLUBB based?

LYSAKERFJORDEN BRETTSEILERKLUBB has its business address in Snarøya.

Property

Business address Rolfstangveien 29, 1367 Snarøya
Cadastral unit 3201-41/155/0/0

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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