biztrac. BETA
COMPANY REGISTER PROFILE
928987515 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other construction installation

VEST BRANNSIKRING AS

Org. no. 928987515 Limited company (AS) Stryn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 84,000
Equity NOK 118,000
Incorporated 2022
Share capital NOK 38,000

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 2025 financial year, show NOK 1.7m in revenue and NOK 84,000 in operating profit.

Former names: BUKOS AS

Key figures · 2025

Revenue
NOK 1.7m
▲ +57 %
Operating profit
NOK 84,000
▲ +144 %
Equity
NOK 118,000
▲ +194 %
Est. value
NOK 492,000

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
21.0%
Very good
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns VEST BRANNSIKRING AS?

VEST BRANNSIKRING AS
NOK 1.7m rev. · NOK 84,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.7m in 2025.

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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.