BIZTRAC BETA
COMPANY REGISTER PROFILE
913572092 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

LUN EIENDOM AS

Org. no. 913572092 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −119,000
Equity NOK −100,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−100k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−119k kr).

LUN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 913572092. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer, konsulentvirksomhet og rådgivning innenfor eiendom, herunder eiendomsutvikling og kjøp/salg av eiendom, samt det som naturlig står i forbindelse med dette, herunder deltagelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −119,000
Equity
NOK −100,000

Financial health · 2024

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

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

Who owns LUN EIENDOM AS?

HEMAHA HOLDING AS
LUN EIENDOM AS
· NOK −119,000 profit

LUN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUN EIENDOM AS

Who owns LUN EIENDOM AS?

HEMAHA HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LUN EIENDOM AS?

Hege Mathea Haugen is registered as general manager of LUN EIENDOM AS.

Where is LUN EIENDOM AS based?

LUN EIENDOM 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.