BIZTRAC BETA
Technical testing and analysis

FIRE SECURITY AS

Org. no. 980339807 Limited company (AS) Kristiansand Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 94.0m
Operating profit NOK 24.0m
Equity NOK 13.8m
Incorporated 1998
Employees 8
Share capital NOK 1.1m

Signals

1 flags
  • Nylig endring 2026-07-27 Aksjekapital registrert 2026-07-27.

FIRE SECURITY AS is registered as a limited company in Kristiansand, Agder with organisation number 980339807. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 1998 and has 8 registered employees. Registered share capital is NOK 1.1m, divided into 1085000 shares. The company's stated purpose is: “Brann- og sikkerhetsteknikk, kjøp og salg av fast eiendom samt kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 94.0m in revenue and NOK 24.0m in operating profit.

Key figures · 2025

Revenue
NOK 94.0m
Operating profit
NOK 24.0m
Equity
NOK 13.8m
Est. value
NOK 94.3m

Financial health · 2025

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

Who owns FIRE SECURITY AS?

FIRE SECURITY HOLDING AS
FIRE SECURITY AS
NOK 94.0m rev. · NOK 24.0m profit

FIRE SECURITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIRE SECURITY AS

Who owns FIRE SECURITY AS?

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

What is the revenue of FIRE SECURITY AS?

FIRE SECURITY AS had revenue of NOK 94.0m in 2025.

Who is the general manager of FIRE SECURITY AS?

Ole Tom Eidjord is registered as general manager of FIRE SECURITY AS.

Where is FIRE SECURITY AS based?

FIRE SECURITY AS has its business address in Kristiansand S.

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.