BIZTRAC BETA
Rental and operating of own or leased real estate

LØRENSKOG HAGEBY BRL 1 HJEMMEL AS

Org. no. 930252956 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

LØRENSKOG HAGEBY BRL 1 HJEMMEL AS is registered as a limited company in Oslo, Oslo with organisation number 930252956. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å ha grunnboksregistrerte rettigheter til fast eiendom, og alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 27,000

Financial health · 2024

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

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

Who owns LØRENSKOG HAGEBY BRL 1 HJEMMEL AS?

LØRENSKOG HAGEBY BORETTSLAG 1
LØRENSKOG HAGEBY BRL 1 HJEMMEL AS
NOK 0 rev. · NOK 0 profit

LØRENSKOG HAGEBY BRL 1 HJEMMEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØRENSKOG HAGEBY BRL 1 HJEMMEL AS

Who owns LØRENSKOG HAGEBY BRL 1 HJEMMEL AS?

LØRENSKOG HAGEBY BORETTSLAG 1 is the largest registered owner, with 100.0%.

What is the revenue of LØRENSKOG HAGEBY BRL 1 HJEMMEL AS?

LØRENSKOG HAGEBY BRL 1 HJEMMEL AS had revenue of NOK 0 in 2024.

Where is LØRENSKOG HAGEBY BRL 1 HJEMMEL AS based?

LØRENSKOG HAGEBY BRL 1 HJEMMEL 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 15.06.2026.

Report a problem

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