biztrac. BETA
COMPANY REGISTER PROFILE
821476992 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

HEIBERGLØKKA BOLIGLAG AS

Org. no. 821476992 Limited company (AS) Oslo Incorporated 1950 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK 2.3m
Equity NOK −23.9m
Incorporated 1950
Share capital NOK 1.1m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−23,9 mill kr).
  • Nylig endring 2026-07-20 Adresseendring registrert 2026-07-20.

HEIBERGLØKKA BOLIGLAG AS is registered as a limited company in Oslo, Oslo with organisation number 821476992. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1950. Registered share capital is NOK 1.1m, divided into 113 shares. The company's stated purpose is: “Bygsling, bebyggelse og drift av eiendommen Kvartal 15 av Tøyen i Oslo.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
▲ +7 %
Operating profit
NOK 2.3m
▲ +113 %
Equity
NOK −23.9m
▼ −0 %

Financial health · 2025

Liquidity
5.30
Very good
Current assets ÷ current liabilities
Profitability
12.1%
Good
Return on total assets
Solidity
-119.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HEIBERGLØKKA BOLIGLAG AS?

No shareholders are registered for HEIBERGLØKKA BOLIGLAG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HEIBERGLØKKA BOLIGLAG AS

What is the revenue of HEIBERGLØKKA BOLIGLAG AS?

HEIBERGLØKKA BOLIGLAG AS had revenue of NOK 8.2m in 2025.

Where is HEIBERGLØKKA BOLIGLAG AS based?

HEIBERGLØKKA BOLIGLAG AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.