BIZTRAC BETA
Other education activities

ALARM & SIKKERHET AS

Org. no. 816210712 Limited company (AS) Øyer Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 91,000
Equity NOK 312,000
Incorporated 2015
Share capital NOK 60,000

ALARM & SIKKERHET AS is registered as a limited company in Øyer, Innlandet with organisation number 816210712. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Tilby brannforebyggende tjenester, brannopplæring og alarmsystemer i Norge.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 91,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 91,000
Equity
NOK 312,000
Est. value
NOK 566,000

Financial health · 2025

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

Who owns ALARM & SIKKERHET AS?

DAG OVE HORSBØL OLSEN
ALARM & SIKKERHET AS
NOK 3.2m rev. · NOK 91,000 profit

ALARM & SIKKERHET AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ALARM & SIKKERHET AS own?

ALARM & SIKKERHET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALARM & SIKKERHET AS

Who owns ALARM & SIKKERHET AS?

DAG OVE HORSBØL OLSEN is the largest registered owner, with 50.0%.

What is the revenue of ALARM & SIKKERHET AS?

ALARM & SIKKERHET AS had revenue of NOK 3.2m in 2025.

Who is the general manager of ALARM & SIKKERHET AS?

Dag Ove Horsbøl Olsen is registered as general manager of ALARM & SIKKERHET AS.

Where is ALARM & SIKKERHET AS based?

ALARM & SIKKERHET AS has its business address in Øyer.

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.