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

KILÅSEN BOLIGSAMEIE

Org. no. 814066282 Condominium flat owner (ESEK) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 257,000
Equity NOK 1.9m
Incorporated 2014

KILÅSEN BOLIGSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 814066282. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2014. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 257,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 257,000
Equity
NOK 1.9m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns KILÅSEN BOLIGSAMEIE?

No shareholders are registered for KILÅSEN BOLIGSAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KILÅSEN BOLIGSAMEIE

What is the revenue of KILÅSEN BOLIGSAMEIE?

KILÅSEN BOLIGSAMEIE had revenue of NOK 3.7m in 2025.

Where is KILÅSEN BOLIGSAMEIE based?

KILÅSEN BOLIGSAMEIE has its business address in Oslo.

Property

Business address v/OBOS Eiendomsforvaltning 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.