BIZTRAC BETA
Computer programming activities

OPSCOM SYSTEMS AS

Org. no. 985745064 Limited company (AS) Bodø Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 14.9m
Operating profit NOK −75,000
Equity NOK 8.7m
Incorporated 2003
Employees 9
Share capital NOK 2.6m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−75k kr).

OPSCOM SYSTEMS AS is registered as a limited company in Bodø, Nordland with organisation number 985745064. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2003 and has 9 registered employees. Registered share capital is NOK 2.6m, divided into 2620 shares. The company's stated purpose is: “Utvikle, drive konsepter for drifting over nettet samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.9m in revenue and NOK −75,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.9m
Operating profit
NOK −75,000
Equity
NOK 8.7m
Est. value
NOK 26.2m

Financial health · 2024

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

Who owns OPSCOM SYSTEMS AS?

NORSK MEGLING & AUKSJON AS
OPSCOM SYSTEMS AS
NOK 14.9m rev. · NOK −75,000 profit

OPSCOM SYSTEMS AS has 17 registered shareholders:

All shareholders and roles →

Which companies does OPSCOM SYSTEMS AS own?

OPSCOM SYSTEMS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OPSCOM SYSTEMS AS

Who owns OPSCOM SYSTEMS AS?

NORSK MEGLING & AUKSJON AS is the largest registered owner, with 25.7%.

What is the revenue of OPSCOM SYSTEMS AS?

OPSCOM SYSTEMS AS had revenue of NOK 14.9m in 2024.

Where is OPSCOM SYSTEMS AS based?

OPSCOM SYSTEMS AS has its business address in Bodø.

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.