BIZTRAC BETA
Rental and operating of own or leased real estate

LIAPARK AS

Org. no. 911697262 Limited company (AS) Ål Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 644,000
Operating profit NOK −612,000
Equity NOK 3.4m
Incorporated 2013
Share capital NOK 294,000

Signals

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

LIAPARK AS is registered as a limited company in Ål, Buskerud with organisation number 911697262. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 294,000, divided into 210 shares. The company's stated purpose is: “Drive med utvikling og etablering av fritidsaktiviteter, oppføring av bygg for andre og salg av tjenester i denne forbindelse, bygging av egne bygg, utleie og salg av eiendom og fremme turistvirksomhet i området.”. The most recent filed accounts, for the 2024 financial year, show NOK 644,000 in revenue and NOK −612,000 in operating profit.

Key figures · 2024

Revenue
NOK 644,000
Operating profit
NOK −612,000
Equity
NOK 3.4m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.7%
Good
Equity as a share of total capital

Who owns LIAPARK AS?

SKRINDO HOLDING AS
LIAPARK AS
NOK 644,000 rev. · NOK −612,000 profit

LIAPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIAPARK AS

Who owns LIAPARK AS?

SKRINDO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIAPARK AS?

LIAPARK AS had revenue of NOK 644,000 in 2024.

Where is LIAPARK AS based?

LIAPARK AS has its business address in Ål.

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.