BIZTRAC BETA
Rental and operating of own or leased real estate

LIUM EIENDOMMER AS

Org. no. 990000468 Limited company (AS) Orkland Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 600,000
Operating profit NOK 189,000
Equity NOK 1.5m
Incorporated 2006
Share capital NOK 680,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LIUM EIENDOMMER AS is registered as a limited company in Orkland, Trøndelag with organisation number 990000468. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 680,000, divided into 1000 shares. The company's stated purpose is: “Utleie og drift av fast eiendom og investering i aksjer og lignende, samt hva hermed står i forbindelse herunder delta i andre virksomheter med tilsvarende formål. ”. The most recent filed accounts, for the 2024 financial year, show NOK 600,000 in revenue and NOK 189,000 in operating profit.

Key figures · 2024

Revenue
NOK 600,000
Operating profit
NOK 189,000
Equity
NOK 1.5m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns LIUM EIENDOMMER AS?

LIUM HOLDING AS
LIUM EIENDOMMER AS
NOK 600,000 rev. · NOK 189,000 profit

LIUM EIENDOMMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIUM EIENDOMMER AS

Who owns LIUM EIENDOMMER AS?

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

What is the revenue of LIUM EIENDOMMER AS?

LIUM EIENDOMMER AS had revenue of NOK 600,000 in 2024.

Where is LIUM EIENDOMMER AS based?

LIUM EIENDOMMER AS has its business address in Meldal.

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.