BIZTRAC BETA
COMPANY REGISTER PROFILE
983640362 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

PARES AS

Org. no. 983640362 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Equity NOK 192,000
Incorporated 2001
Share capital NOK 100,000

PARES AS is registered as a limited company in Oslo, Oslo with organisation number 983640362. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive konsulent og incubatorvirksomhet, deltakelse i andre selskaper, samt virksomhet forbundet med dette.”.

Key figures · 2025

Equity
NOK 192,000
Est. value
NOK 313,000

Financial health · 2025

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

Who owns PARES AS?

PARES AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PARES AS own?

PARES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PARES AS

Who owns PARES AS?

ARE STRAY is the largest registered owner, with 51.0%.

Who is the general manager of PARES AS?

Are Stray is registered as general manager of PARES AS.

Where is PARES AS based?

PARES AS has its business address in Oslo.

Property

Business address Søndre Rød 5B, 0752 Oslo
Cadastral unit 301-11/517/0/0
Building Rekkehus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.