BIZTRAC BETA
Buying and selling of own real estate

LISØ INVEST AS

Org. no. 918331247 Limited company (AS) Sarpsborg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −130,000
Equity NOK 9.3m
Incorporated 2016
Share capital NOK 30,000

Signals

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

LISØ INVEST AS is registered as a limited company in Sarpsborg, Østfold with organisation number 918331247. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Erverv og forvaltning av aksjer og eierandeler i andre foretak samt eiendomsinvesteringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −130,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −130,000
Equity
NOK 9.3m
Est. value
NOK 18.2m

Financial health · 2024

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

Who owns LISØ INVEST AS?

ØRJAN ÅDALEN
LISØ INVEST AS
NOK 0 rev. · NOK −130,000 profit

LISØ INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LISØ INVEST AS own?

LISØ INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about LISØ INVEST AS

Who owns LISØ INVEST AS?

ØRJAN ÅDALEN is the largest registered owner, with 100.0%.

What is the revenue of LISØ INVEST AS?

LISØ INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of LISØ INVEST AS?

Ørjan Ådalen is registered as general manager of LISØ INVEST AS.

Where is LISØ INVEST AS based?

LISØ INVEST AS has its business address in Yven.

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.