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

NADDERUDVEIEN 1 SAMEIE

Org. no. 928032507 Condominium flat owner (ESEK) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Equity NOK 152,000
Incorporated 2021

NADDERUDVEIEN 1 SAMEIE is registered as a condominium flat owner in Bærum, Akershus with organisation number 928032507. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2021. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue.

Key figures · 2025

Revenue
NOK 4.1m
Equity
NOK 152,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns NADDERUDVEIEN 1 SAMEIE?

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

Frequently asked questions about NADDERUDVEIEN 1 SAMEIE

What is the revenue of NADDERUDVEIEN 1 SAMEIE?

NADDERUDVEIEN 1 SAMEIE had revenue of NOK 4.1m in 2025.

Where is NADDERUDVEIEN 1 SAMEIE based?

NADDERUDVEIEN 1 SAMEIE has its business address in Sandvika.

Property

Business address Kinoveien 3, 1337 Sandvika
Cadastral unit 3201-7/39/0/0
Building Kontor- og administrasjonsbygning, rådhus · 14 units

83 companies are registered at this address.

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.