BIZTRAC BETA
Rental and operating of own or leased real estate

LIE EIENDOM AS

Org. no. 983189369 Limited company (AS) Våler Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 44,000
Operating profit NOK −43,000
Equity NOK 985,000
Incorporated 2001
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).

LIE EIENDOM AS is registered as a limited company in Våler, Innlandet with organisation number 983189369. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Handel med og utleie av driftsmidler og eiendom, handel med aksjer og verdipapirer, samt det som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 44,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 44,000
Operating profit
NOK −43,000
Equity
NOK 985,000
Est. value
NOK 688,000

Financial health · 2025

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

Who owns LIE EIENDOM AS?

SIGURD BERNHARD LIE
LIE EIENDOM AS
NOK 44,000 rev. · NOK −43,000 profit

LIE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIE EIENDOM AS

Who owns LIE EIENDOM AS?

SIGURD BERNHARD LIE is the largest registered owner, with 100.0%.

What is the revenue of LIE EIENDOM AS?

LIE EIENDOM AS had revenue of NOK 44,000 in 2025.

Who is the general manager of LIE EIENDOM AS?

Sigurd Bernhard Lie is registered as general manager of LIE EIENDOM AS.

Where is LIE EIENDOM AS based?

LIE EIENDOM AS has its business address in Våler I Solør.

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.