BIZTRAC BETA
Buying and selling of own real estate

LIEN HOLDING PROSJEKT AS

Org. no. 925176559 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 25,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

LIEN HOLDING PROSJEKT AS is registered as a limited company in Asker, Akershus with organisation number 925176559. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Holdingselskap og alt som hører naturlig til dette.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 25,000
Est. value
NOK 23,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LIEN HOLDING PROSJEKT AS?

GISLE ALSÅKER LIEN
LIEN HOLDING PROSJEKT AS
· NOK −1,000 profit

LIEN HOLDING PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIEN HOLDING PROSJEKT AS own?

LIEN HOLDING PROSJEKT AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

LIEN HOLDING PROSJEKT AS er morselskap for 2 datterselskaper:

Frequently asked questions about LIEN HOLDING PROSJEKT AS

Who owns LIEN HOLDING PROSJEKT AS?

GISLE ALSÅKER LIEN is the largest registered owner, with 100.0%.

Who is the general manager of LIEN HOLDING PROSJEKT AS?

Gisle Alsåker Lien is registered as general manager of LIEN HOLDING PROSJEKT AS.

Where is LIEN HOLDING PROSJEKT AS based?

LIEN HOLDING PROSJEKT AS has its business address in Asker.

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.