BIZTRAC BETA
Other construction installation

VEST BRANNSIKRING AS

Org. no. 928987515 Limited company (AS) Stryn Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −188,000
Equity NOK 40,000
Incorporated 2022
Share capital NOK 38,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−188k kr).

VEST BRANNSIKRING AS is registered as a limited company in Stryn, Vestland with organisation number 928987515. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2022. Registered share capital is NOK 38,000, divided into 30000 shares. The company's stated purpose is: “Utførelse av installasjoner og bygningsdeler med brannteknisk funksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −188,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −188,000
Equity
NOK 40,000
Est. value
NOK 387,000

Financial health · 2024

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Weak
Equity as a share of total capital

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

Who owns VEST BRANNSIKRING AS?

KJELL OVE STEIN
VEST BRANNSIKRING AS
NOK 1.1m rev. · NOK −188,000 profit

VEST BRANNSIKRING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEST BRANNSIKRING AS

Who owns VEST BRANNSIKRING AS?

KJELL OVE STEIN is the largest registered owner, with 50.0%.

What is the revenue of VEST BRANNSIKRING AS?

VEST BRANNSIKRING AS had revenue of NOK 1.1m in 2024.

Who is the general manager of VEST BRANNSIKRING AS?

Kjell Ove Stein is registered as general manager of VEST BRANNSIKRING AS.

Where is VEST BRANNSIKRING AS based?

VEST BRANNSIKRING AS has its business address in Stryn.

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.