biztrac. BETA
COMPANY REGISTER PROFILE
923126090 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

AS PARKGAARDEN HOLDING

Org. no. 923126090 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −958,000
Equity NOK 124.1m
Incorporated 2019
Share capital NOK 300,000

Signals

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

AS PARKGAARDEN HOLDING is registered as a limited company in Oslo, Oslo with organisation number 923126090. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, selskapsandeler eller andre verdipapirer, fast eiendom og deltagelse i andre virksomheter, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −958,000
▼ −4840 %
Equity
NOK 124.1m
▲ +1348 %
Est. value
NOK 862.5m

Financial health · 2025

Liquidity
42.09
Very good
Current assets ÷ current liabilities
Profitability
178.1%
Very good
Return on total assets
Solidity
97.7%
Very good
Equity as a share of total capital

Who owns AS PARKGAARDEN HOLDING?

AS PARKGAARDEN HOLDING
· NOK −958,000 profit

AS PARKGAARDEN HOLDING has 1 registered shareholder:

All shareholders and roles →

Which companies does AS PARKGAARDEN HOLDING own?

AS PARKGAARDEN HOLDING holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AS PARKGAARDEN HOLDING

Who owns AS PARKGAARDEN HOLDING?

Inger Frydenlund Bugge is the largest registered owner, with 100.0%.

Who is the general manager of AS PARKGAARDEN HOLDING?

Inger Frydenlund Bugge is registered as general manager of AS PARKGAARDEN HOLDING.

Where is AS PARKGAARDEN HOLDING based?

AS PARKGAARDEN HOLDING has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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