BIZTRAC BETA
Rental and operating of own or leased real estate

LISTA FLYPARK HOLDING AS

Org. no. 991410015 Limited company (AS) Farsund Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −48,000
Equity NOK 26.3m
Incorporated 2007
Share capital NOK 15.1m

Signals

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

LISTA FLYPARK HOLDING AS is registered as a limited company in Farsund, Agder with organisation number 991410015. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 15.1m, divided into 30144 shares. The company's stated purpose is: “Investere i samt å la oppføre fast eiendom samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −48,000
Equity
NOK 26.3m
Est. value
NOK 24.0m

Financial health · 2024

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

Who owns LISTA FLYPARK HOLDING AS?

LISTA FLYPARK INVEST AS
LISTA FLYPARK HOLDING AS
· NOK −48,000 profit

LISTA FLYPARK HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does LISTA FLYPARK HOLDING AS own?

LISTA FLYPARK HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LISTA FLYPARK HOLDING AS

Who owns LISTA FLYPARK HOLDING AS?

LISTA FLYPARK INVEST AS is the largest registered owner, with 74.8%.

Who is the general manager of LISTA FLYPARK HOLDING AS?

Helge Dagfinn Mikalsen is registered as general manager of LISTA FLYPARK HOLDING AS.

Where is LISTA FLYPARK HOLDING AS based?

LISTA FLYPARK HOLDING AS has its business address in Vanse.

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.