BIZTRAC BETA
Security activities n.e.c.

VERISURE AS

Org. no. 929120825 Limited company (AS) Oslo Incorporated 1965 Active
Ownership graph ↗
Revenue 2024 NOK 1.4bn
Operating profit NOK 260.7m
Equity NOK 4.3m
Incorporated 1965
Employees 385
Share capital NOK 2.0m

Signals

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

VERISURE AS is registered as a limited company in Oslo, Oslo with organisation number 929120825. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 1965 and has 385 registered employees. Registered share capital is NOK 2.0m, divided into 8000 shares. The company's stated purpose is: “Besørge salg og service av alarmanlegg med tilhørende tjenester og annen beslektet forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4bn in revenue and NOK 260.7m in operating profit.

Key figures · 2024

Revenue
NOK 1.4bn
Operating profit
NOK 260.7m
Equity
NOK 4.3m
Est. value
NOK 720.2m

Financial health · 2024

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.2%
Not satisfactory
Equity as a share of total capital

Who owns VERISURE AS?

VERISURE HOLDING AS
VERISURE AS
NOK 1.4bn rev. · NOK 260.7m profit

VERISURE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VERISURE AS er morselskap for 1 datterselskap:

Frequently asked questions about VERISURE AS

Who owns VERISURE AS?

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

What is the revenue of VERISURE AS?

VERISURE AS had revenue of NOK 1.4bn in 2024.

Who is the general manager of VERISURE AS?

Anders Boger is registered as general manager of VERISURE AS.

Where is VERISURE AS based?

VERISURE 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.