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

LILLEPARKEN BORETTSLAG

Org. no. 850047812 Housing cooperative (BRL) Oslo Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 836,000
Equity NOK 17.2m
Incorporated 1985

LILLEPARKEN BORETTSLAG is registered as a housing cooperative in Oslo, Oslo with organisation number 850047812. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1985. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 836,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 836,000
Equity
NOK 17.2m
Est. value
NOK 12.2m

Financial health · 2025

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

Who owns LILLEPARKEN BORETTSLAG?

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

Frequently asked questions about LILLEPARKEN BORETTSLAG

What is the revenue of LILLEPARKEN BORETTSLAG?

LILLEPARKEN BORETTSLAG had revenue of NOK 2.8m in 2025.

Where is LILLEPARKEN BORETTSLAG based?

LILLEPARKEN BORETTSLAG has its business address in Oslo.

Property

Business address c/o OBOS 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.