BIZTRAC BETA
Electrical installation

BOLIGALARM AS

Org. no. 994276514 Limited company (AS) Vestvågøy Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −1.1m
Equity NOK −1.1m
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

BOLIGALARM AS is registered as a limited company in Vestvågøy, Nordland with organisation number 994276514. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, service og installasjon av sikkerhetstjenester og sikkerhetsutstyr for private og næring.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −1.1m
Equity
NOK −1.1m

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-306.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BOLIGALARM AS?

ARTHUR JOHAN JOHNSEN
BOLIGALARM AS
NOK 2.5m rev. · NOK −1.1m profit

BOLIGALARM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGALARM AS

Who owns BOLIGALARM AS?

ARTHUR JOHAN JOHNSEN is the largest registered owner, with 100.0%.

What is the revenue of BOLIGALARM AS?

BOLIGALARM AS had revenue of NOK 2.5m in 2025.

Who is the general manager of BOLIGALARM AS?

Arthur Johan Johnsen is registered as general manager of BOLIGALARM AS.

Where is BOLIGALARM AS based?

BOLIGALARM AS has its business address in Leknes.

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.