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

SAMEIET KIRKEVEIEN 77

Org. no. 983608442 Condominium flat owner (ESEK) Oslo Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 139,000
Equity NOK 256,000
Incorporated 1991

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

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 139,000
Equity
NOK 256,000
Est. value
NOK 642,000

Financial health · 2025

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

Who owns SAMEIET KIRKEVEIEN 77?

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

Frequently asked questions about SAMEIET KIRKEVEIEN 77

What is the revenue of SAMEIET KIRKEVEIEN 77?

SAMEIET KIRKEVEIEN 77 had revenue of NOK 1.4m in 2025.

Where is SAMEIET KIRKEVEIEN 77 based?

SAMEIET KIRKEVEIEN 77 has its business address in Oslo.

Property

Business address c/o Nor Forvaltning AS Alnaparkveien 11, 1081 Oslo
Cadastral unit 301-112/201/0/0
Building Fabrikkbygning · 1 unit

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