BIZTRAC BETA
COMPANY REGISTER PROFILE
925786543 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

LISTA FLYPARK INVEST AS

Org. no. 925786543 Limited company (AS) Farsund Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 635,000
Incorporated 2020
Share capital NOK 750,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LISTA FLYPARK INVEST AS is registered as a limited company in Farsund, Agder with organisation number 925786543. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 750,000, divided into 7500 shares. The company's stated purpose is: “Investeringer og deltakelse i andre selskaper og eiendom, rådgivning, samt alt som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −38,000
▼ −40 %
Equity
NOK 635,000
▼ −4 %
Est. value
NOK 579,000

Financial health · 2025

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

Who owns LISTA FLYPARK INVEST AS?

LISTA FLYPARK INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LISTA FLYPARK INVEST AS own?

LISTA FLYPARK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LISTA FLYPARK INVEST AS

Who owns LISTA FLYPARK INVEST AS?

VOLLAN HOLDING AS is the largest registered owner, with 33.3%.

Where is LISTA FLYPARK INVEST AS based?

LISTA FLYPARK INVEST 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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.