BIZTRAC BETA
Other manufacturing n.e.c.

OPTIMEK AS

Org. no. 918074597 Limited company (AS) Gjerstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 50.9m
Operating profit NOK 609,000
Equity NOK 3.6m
Incorporated 2016
Employees 22
Share capital NOK 800,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OPTIMEK AS is registered as a limited company in Gjerstad, Agder with organisation number 918074597. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 2016 and has 22 registered employees. Registered share capital is NOK 800,000, divided into 100 shares. The company's stated purpose is: “Produksjonsvirksomhet innenfor industri, bergverk, anleggsmaskiner, olje - og gassvirksomhet og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.9m in revenue and NOK 609,000 in operating profit.

Key figures · 2024

Revenue
NOK 50.9m
Operating profit
NOK 609,000
Equity
NOK 3.6m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.3%
Good
Equity as a share of total capital

Who owns OPTIMEK AS?

OPTIMEK HOLDING AS
OPTIMEK AS
NOK 50.9m rev. · NOK 609,000 profit

OPTIMEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPTIMEK AS

Who owns OPTIMEK AS?

OPTIMEK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OPTIMEK AS?

OPTIMEK AS had revenue of NOK 50.9m in 2024.

Who is the general manager of OPTIMEK AS?

Tor Markussen is registered as general manager of OPTIMEK AS.

Where is OPTIMEK AS based?

OPTIMEK AS has its business address in Sundebru.

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.