BIZTRAC BETA
Manufacture of electronic components

INTEGRATED OPTOELECTRONICS AS

Org. no. 985910731 Limited company (AS) Trondheim Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −1.5m
Equity NOK 7.2m
Incorporated 2003
Share capital NOK 11.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).
  • Nylig endring 2026-04-24 Adresseendring registrert 2026-04-24.

INTEGRATED OPTOELECTRONICS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 985910731. The business is classified under manufacture of electronic components (NACE 26.110). The company was incorporated in 2003. Registered share capital is NOK 11.1m, divided into 44598666 shares. The company's stated purpose is: “Konsultasjon på og produksjon av elektrooptiske nano- og mikro-systemer for sensorteknologi og kommunikasjon, samt deltagelse i selskaper av samme eller annen art gjennom aksjetegning eller på annen måte.”.

Key figures · 2024

Operating profit
NOK −1.5m
Equity
NOK 7.2m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns INTEGRATED OPTOELECTRONICS AS?

LBT HOLDING AS
INTEGRATED OPTOELECTRONICS AS
· NOK −1.5m profit

INTEGRATED OPTOELECTRONICS AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does INTEGRATED OPTOELECTRONICS AS own?

INTEGRATED OPTOELECTRONICS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about INTEGRATED OPTOELECTRONICS AS

Who owns INTEGRATED OPTOELECTRONICS AS?

LBT HOLDING AS is the largest registered owner, with 13.4%.

Where is INTEGRATED OPTOELECTRONICS AS based?

INTEGRATED OPTOELECTRONICS AS has its business address in Trondheim.

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.