BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

PARIO TRADING AS

Org. no. 990755345 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 491,000
Operating profit NOK 141,000
Equity NOK 8.1m
Incorporated 2007
Share capital NOK 50,000

PARIO TRADING AS is registered as a limited company in Asker, Akershus with organisation number 990755345. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2007. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Import av varer, konsulentvirksomhet og investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 491,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2024

Revenue
NOK 491,000
Operating profit
NOK 141,000
Equity
NOK 8.1m
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
2.20
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.1%
Very good
Equity as a share of total capital

Who owns PARIO TRADING AS?

ANDRÉ BACKEN
PARIO TRADING AS
NOK 491,000 rev. · NOK 141,000 profit

PARIO TRADING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PARIO TRADING AS own?

PARIO TRADING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about PARIO TRADING AS

Who owns PARIO TRADING AS?

ANDRÉ BACKEN is the largest registered owner, with 100.0%.

What is the revenue of PARIO TRADING AS?

PARIO TRADING AS had revenue of NOK 491,000 in 2024.

Who is the general manager of PARIO TRADING AS?

André Backen is registered as general manager of PARIO TRADING AS.

Where is PARIO TRADING AS based?

PARIO TRADING AS has its business address in Nesøya.

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.