BIZTRAC BETA
Development of building projects

LIASET EIENDOM AS

Org. no. 914309034 Limited company (AS) Nesbyen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.1m
Equity NOK 63.3m
Incorporated 2014
Share capital NOK 60,000

LIASET EIENDOM AS is registered as a limited company in Nesbyen, Buskerud with organisation number 914309034. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Investere i, utvikle, eie, drive, forvalte og omsette tomter og eiendom av enhver art, og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.1m
Equity
NOK 63.3m
Est. value
NOK 47.5m

Financial health · 2024

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

Who owns LIASET EIENDOM AS?

ARNEGÅRD HOLDING AS
LIASET EIENDOM AS
NOK 3.1m rev. · NOK 1.1m profit

LIASET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIASET EIENDOM AS own?

LIASET EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIASET EIENDOM AS

Who owns LIASET EIENDOM AS?

ARNEGÅRD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIASET EIENDOM AS?

LIASET EIENDOM AS had revenue of NOK 3.1m in 2024.

Who is the general manager of LIASET EIENDOM AS?

Bernhard Tandberg is registered as general manager of LIASET EIENDOM AS.

Where is LIASET EIENDOM AS based?

LIASET EIENDOM AS has its business address in Nesbyen.

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.