BIZTRAC BETA
Manufacture of jewellery and related articles

OPRO PRODUKTER AS

Org. no. 913082303 Limited company (AS) Oslo Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 6.7m
Operating profit NOK 1.3m
Equity NOK 8.6m
Incorporated 1976
Employees 8
Share capital NOK 100,000

OPRO PRODUKTER AS is registered as a limited company in Oslo, Oslo with organisation number 913082303. The business is classified under manufacture of jewellery and related articles (NACE 32.120). The company was incorporated in 1976 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Produksjon, tilvirkning og omsetning av gull og sølvsmedartikler og det som derved står i for- bindelse, samt ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.7m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 6.7m
Operating profit
NOK 1.3m
Equity
NOK 8.6m
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns OPRO PRODUKTER AS?

JUNE RASCH-OLSEN
OPRO PRODUKTER AS
NOK 6.7m rev. · NOK 1.3m profit

OPRO PRODUKTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPRO PRODUKTER AS

Who owns OPRO PRODUKTER AS?

JUNE RASCH-OLSEN is the largest registered owner, with 96.0%.

What is the revenue of OPRO PRODUKTER AS?

OPRO PRODUKTER AS had revenue of NOK 6.7m in 2024.

Who is the general manager of OPRO PRODUKTER AS?

June Rasch-Olsen is registered as general manager of OPRO PRODUKTER AS.

Where is OPRO PRODUKTER AS based?

OPRO PRODUKTER 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.