BIZTRAC BETA
Business and other management consultancy activities

PETROADVISOR AS

Org. no. 981409442 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −263,000
Equity NOK 178,000
Incorporated 1999
Share capital NOK 30,000

Signals

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

PETROADVISOR AS is registered as a limited company in Oslo, Oslo with organisation number 981409442. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1999. Registered share capital is NOK 30,000, divided into 1737 shares. The company's stated purpose is: “Drive rådgivningsvirksomhet og megling, primært relatert til olje og gass sektoren i Norge og internasonalt, samt investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −263,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −263,000
Equity
NOK 178,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns PETROADVISOR AS?

CORDATUM INVEST AS
PETROADVISOR AS
NOK 1.1m rev. · NOK −263,000 profit

PETROADVISOR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PETROADVISOR AS

Who owns PETROADVISOR AS?

CORDATUM INVEST AS is the largest registered owner, with 33.4%.

What is the revenue of PETROADVISOR AS?

PETROADVISOR AS had revenue of NOK 1.1m in 2025.

Who is the general manager of PETROADVISOR AS?

Fridtjof Arne Jebsen is registered as general manager of PETROADVISOR AS.

Where is PETROADVISOR AS based?

PETROADVISOR AS has its business address in Oslo.

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.