BIZTRAC BETA
Business and other management consultancy activities

LED EIENDOM AS

Org. no. 926401998 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −291,000
Equity NOK 9.7m
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−291k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LED EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 926401998. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, rådgivning, forvaltning, utvikling og drift innen eiendom, samt all annen virksomhet som kan henføres til dette. Dette innebærer også blant annet, men er ikke begrenset til, direkte investeringer, samt investeringer i aksjer, andre verdipapirer og finansielle instrumenter.”.

Key figures · 2025

Operating profit
NOK −291,000
Equity
NOK 9.7m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns LED EIENDOM AS?

MILIARIUM HOLDING AS
LED EIENDOM AS
· NOK −291,000 profit

LED EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LED EIENDOM AS own?

LED EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LED EIENDOM AS

Who owns LED EIENDOM AS?

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

Where is LED EIENDOM AS based?

LED 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.