BIZTRAC BETA
COMPANY REGISTER PROFILE
915336922 ORG. NO. 2020 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

KAPELLVEIEN SAMEIE

Org. no. 915336922 Condominium flat owner (ESEK) Nesodden Incorporated 2002 Active
Ownership graph ↗
Revenue 2020 NOK 103,000
Operating profit NOK 24,000
Equity NOK 0
Incorporated 2002

KAPELLVEIEN SAMEIE is registered as a condominium flat owner in Nesodden, Akershus with organisation number 915336922. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2002. The most recent filed accounts, for the 2020 financial year, show NOK 103,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2020

Revenue
NOK 103,000
Operating profit
NOK 24,000
Equity
NOK 0
Est. value
NOK 121,000

Financial health · 2020

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KAPELLVEIEN SAMEIE?

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

Frequently asked questions about KAPELLVEIEN SAMEIE

What is the revenue of KAPELLVEIEN SAMEIE?

KAPELLVEIEN SAMEIE had revenue of NOK 103,000 in 2020.

Where is KAPELLVEIEN SAMEIE based?

KAPELLVEIEN SAMEIE has its business address in Nesoddtangen.

Property

Business address Kapellveien 109, 1452 Nesoddtangen
Cadastral unit 3212-2/371/0/0
Building Rekkehus · 1 unit

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.