BIZTRAC BETA
Wholesale of perfume and cosmetics

PAGRO AS

Org. no. 928085635 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK −296,000
Incorporated 2021
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−296k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

PAGRO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 928085635. The business is classified under wholesale of perfume and cosmetics (NACE 46.450). The company was incorporated in 2021. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Handelsvirksomhet med kosmetiske produkter, samt virksomhet som står i forbindelse med dette, herunder deltakelse i andre lignende foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −296,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PAGRO AS?

E H SLYNGSTAD AS
PAGRO AS
NOK 0 rev. · NOK −18,000 profit

PAGRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAGRO AS

Who owns PAGRO AS?

E H SLYNGSTAD AS is the largest registered owner, with 100.0%.

What is the revenue of PAGRO AS?

PAGRO AS had revenue of NOK 0 in 2025.

Who is the general manager of PAGRO AS?

Holger Slyngstad is registered as general manager of PAGRO AS.

Where is PAGRO AS based?

PAGRO AS has its business address in Ålesund.

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.