BIZTRAC BETA
Electrical installation

ØSTFOLD ALARMTJENESTER AS

Org. no. 928029700 Limited company (AS) Moss Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 17.3m
Operating profit NOK 402,000
Equity NOK 597,000
Incorporated 2021
Employees 13
Share capital NOK 30,000

ØSTFOLD ALARMTJENESTER AS is registered as a limited company in Moss, Østfold with organisation number 928029700. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2021 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Salg, installasjon og service på alarmanlegg og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.3m in revenue and NOK 402,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.3m
Operating profit
NOK 402,000
Equity
NOK 597,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns ØSTFOLD ALARMTJENESTER AS?

PÅL BRYNJAR NYBØ
ØSTFOLD ALARMTJENESTER AS
NOK 17.3m rev. · NOK 402,000 profit

ØSTFOLD ALARMTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTFOLD ALARMTJENESTER AS

Who owns ØSTFOLD ALARMTJENESTER AS?

PÅL BRYNJAR NYBØ is the largest registered owner, with 100.0%.

What is the revenue of ØSTFOLD ALARMTJENESTER AS?

ØSTFOLD ALARMTJENESTER AS had revenue of NOK 17.3m in 2024.

Who is the general manager of ØSTFOLD ALARMTJENESTER AS?

Dennis Leknessund Gjerstad is registered as general manager of ØSTFOLD ALARMTJENESTER AS.

Where is ØSTFOLD ALARMTJENESTER AS based?

ØSTFOLD ALARMTJENESTER AS has its business address in Dilling.

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.