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

SAMEIET KIRKEVEIEN 51

Org. no. 981269616 Condominium flat owner (ESEK) Oslo Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 75,000
Equity NOK 164,000
Incorporated 1984

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

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 75,000
Equity
NOK 164,000
Est. value
NOK 387,000

Financial health · 2025

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

Who owns SAMEIET KIRKEVEIEN 51?

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

Frequently asked questions about SAMEIET KIRKEVEIEN 51

What is the revenue of SAMEIET KIRKEVEIEN 51?

SAMEIET KIRKEVEIEN 51 had revenue of NOK 1.3m in 2025.

Where is SAMEIET KIRKEVEIEN 51 based?

SAMEIET KIRKEVEIEN 51 has its business address in Oslo.

Property

Business address Kirkeveien 51, 0368 Oslo
Cadastral unit 301-215/163/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 19 units

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