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

PARKGÅRDEN AS

Org. no. 984939833 Limited company (AS) Molde Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −696,000
Equity NOK 8.7m
Incorporated 2002
Share capital NOK 7.5m

Signals

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

PARKGÅRDEN AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 984939833. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 7.5m, divided into 7500 shares. The company's stated purpose is: “Oppføre, forvalte/drive utleie, eventuelt omsetning av fast eiendom, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignede virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −696,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▲ +24 %
Operating profit
NOK −696,000
▼ −220 %
Equity
NOK 8.7m
▲ +15 %
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
4.89
Very good
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
22.0%
Good
Equity as a share of total capital

Who owns PARKGÅRDEN AS?

PARKGÅRDEN AS
NOK 2.3m rev. · NOK −696,000 profit

PARKGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARKGÅRDEN AS

Who owns PARKGÅRDEN AS?

ANGVIK AREAL AS is the largest registered owner, with 100.0%.

What is the revenue of PARKGÅRDEN AS?

PARKGÅRDEN AS had revenue of NOK 2.3m in 2025.

Where is PARKGÅRDEN AS based?

PARKGÅRDEN AS has its business address in Molde.

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.