BIZTRAC BETA
Rental and operating of own or leased real estate

LIERSKOGEN EIENDOM AS

Org. no. 911854481 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 3.3m
Equity NOK 20.6m
Incorporated 2013
Share capital NOK 1.0m

Signals

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

LIERSKOGEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 911854481. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 3.3m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 3.3m
Equity
NOK 20.6m
Est. value
NOK 21.8m

Financial health · 2024

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

Who owns LIERSKOGEN EIENDOM AS?

NORGESGRUPPEN EIENDOM BUSKERUD AS
LIERSKOGEN EIENDOM AS
NOK 4.2m rev. · NOK 3.3m profit

LIERSKOGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LIERSKOGEN EIENDOM AS er morselskap for 249 datterselskaper:

Frequently asked questions about LIERSKOGEN EIENDOM AS

Who owns LIERSKOGEN EIENDOM AS?

NORGESGRUPPEN EIENDOM BUSKERUD AS is the largest registered owner, with 100.0%.

What is the revenue of LIERSKOGEN EIENDOM AS?

LIERSKOGEN EIENDOM AS had revenue of NOK 4.2m in 2024.

Where is LIERSKOGEN EIENDOM AS based?

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