BIZTRAC BETA
Security activities n.e.c.

SECTOR ALARM MIDCO AS

Org. no. 920349390 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −117,000
Equity NOK 11.4bn
Incorporated 2018
Share capital NOK 5.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−117k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SECTOR ALARM MIDCO AS is registered as a limited company in Oslo, Oslo with organisation number 920349390. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2018. Registered share capital is NOK 5.2m, divided into 1100033 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå vaktvirksomhet samt montering og vedlikehold av sikkerhetsutstyr knyttet til virksomheten overfor private husholdninger, samt hva dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −117,000
Equity
NOK 11.4bn
Est. value
NOK 16.4bn

Financial health · 2024

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

Who owns SECTOR ALARM MIDCO AS?

SECTOR ALARM TOPCO AS
SECTOR ALARM MIDCO AS
· NOK −117,000 profit

SECTOR ALARM MIDCO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SECTOR ALARM MIDCO AS own?

SECTOR ALARM MIDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SECTOR ALARM MIDCO AS

Who owns SECTOR ALARM MIDCO AS?

SECTOR ALARM TOPCO AS is the largest registered owner, with 89.3%.

Where is SECTOR ALARM MIDCO AS based?

SECTOR ALARM MIDCO 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.