BIZTRAC BETA
Research and experimental development on natural sciences and engineering

PETRAOS AS

Org. no. 921887264 Limited company (AS) Øygarden Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 32,000
Operating profit NOK 26,000
Equity NOK 48,000
Incorporated 2018
Share capital NOK 30,000

PETRAOS AS is registered as a limited company in Øygarden, Vestland with organisation number 921887264. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Utvikling, teknologisk tilpasning, produksjon, salg, fabrikasjon, bruk og rådgivning for nano- og mikroskopisk skalert materiale eller enheter laget av den og tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 32,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 32,000
Operating profit
NOK 26,000
Equity
NOK 48,000
Est. value
NOK 96,000

Financial health · 2025

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

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

Who owns PETRAOS AS?

ALLA SAPRONOVA
PETRAOS AS
NOK 32,000 rev. · NOK 26,000 profit

PETRAOS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PETRAOS AS

Who owns PETRAOS AS?

ALLA SAPRONOVA is the largest registered owner, with 100.0%.

What is the revenue of PETRAOS AS?

PETRAOS AS had revenue of NOK 32,000 in 2025.

Who is the general manager of PETRAOS AS?

Alla Sapronova is registered as general manager of PETRAOS AS.

Where is PETRAOS AS based?

PETRAOS AS has its business address in Straume.

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.