BIZTRAC BETA
Manufacture of other pumps and compressors

OPTIMARIN AS

Org. no. 970942327 Limited company (AS) Sandnes Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 249.0m
Operating profit NOK 17.8m
Equity NOK 93.4m
Incorporated 1994
Employees 39
Share capital NOK 7.5m

Signals

1 flags
  • Nylig endring 2026-06-25 Adresseendring registrert 2026-06-25.

OPTIMARIN AS is registered as a limited company in Sandnes, Rogaland with organisation number 970942327. The business is classified under manufacture of other pumps and compressors (NACE 28.130). The company was incorporated in 1994 and has 39 registered employees. Registered share capital is NOK 7.5m, divided into 7470809 shares. The company's stated purpose is: “Utvikling, produksjon, representasjon og handel, konsulent og agentvirksomhet, herunder å delta i andre selskaper med lignende eller annen virksomhet. ”. The most recent filed accounts, for the 2025 financial year, show NOK 249.0m in revenue and NOK 17.8m in operating profit.

Key figures · 2025

Revenue
NOK 249.0m
Operating profit
NOK 17.8m
Equity
NOK 93.4m
Est. value
NOK 119.5m

Financial health · 2025

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

Who owns OPTIMARIN AS?

KLAVENESS INVEST AS
OPTIMARIN AS
NOK 249.0m rev. · NOK 17.8m profit

OPTIMARIN AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about OPTIMARIN AS

Who owns OPTIMARIN AS?

KLAVENESS INVEST AS is the largest registered owner, with 40.8%.

What is the revenue of OPTIMARIN AS?

OPTIMARIN AS had revenue of NOK 249.0m in 2025.

Who is the general manager of OPTIMARIN AS?

Tore Martin Svanheld is registered as general manager of OPTIMARIN AS.

Where is OPTIMARIN AS based?

OPTIMARIN AS has its business address in Sandnes.

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.