BIZTRAC BETA
Uoppgitt

LIEN BOLIGINVEST AS

Org. no. 821457092 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −326,000
Equity NOK 3.0m
Incorporated 2018
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−326k kr).

LIEN BOLIGINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 821457092. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendomsrelaterte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −326,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −326,000
Equity
NOK 3.0m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns LIEN BOLIGINVEST AS?

LIEN EIENDOMSUTVIKLING AS
LIEN BOLIGINVEST AS
NOK 0 rev. · NOK −326,000 profit

LIEN BOLIGINVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIEN BOLIGINVEST AS own?

LIEN BOLIGINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIEN BOLIGINVEST AS

Who owns LIEN BOLIGINVEST AS?

LIEN EIENDOMSUTVIKLING AS is the largest registered owner, with 50.0%.

What is the revenue of LIEN BOLIGINVEST AS?

LIEN BOLIGINVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of LIEN BOLIGINVEST AS?

Nils Thomas Lien is registered as general manager of LIEN BOLIGINVEST AS.

Where is LIEN BOLIGINVEST AS based?

LIEN BOLIGINVEST 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.