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

SAMEIET HØYENHALLVEIEN 2

Org. no. 996014908 Condominium flat owner (ESEK) Oslo Incorporated 1974 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 134,000
Equity NOK 747,000
Incorporated 1974

SAMEIET HØYENHALLVEIEN 2 is registered as a condominium flat owner in Oslo, Oslo with organisation number 996014908. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1974. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 134,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 134,000
Equity
NOK 747,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns SAMEIET HØYENHALLVEIEN 2?

No shareholders are registered for SAMEIET HØYENHALLVEIEN 2 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET HØYENHALLVEIEN 2

What is the revenue of SAMEIET HØYENHALLVEIEN 2?

SAMEIET HØYENHALLVEIEN 2 had revenue of NOK 1.3m in 2025.

Where is SAMEIET HØYENHALLVEIEN 2 based?

SAMEIET HØYENHALLVEIEN 2 has its business address in Oslo.

Property

Business address c/o OEF AS Hammersborg torg 1, 0179 Oslo
Cadastral unit 301-208/279/0/0

1650 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.