BIZTRAC BETA
Other technical consultancy

VBM BRANNSIKRING AS

Org. no. 929022580 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 364,000
Equity NOK 744,000
Incorporated 2022
Employees 9
Share capital NOK 200,000

VBM BRANNSIKRING AS is registered as a limited company in Asker, Akershus with organisation number 929022580. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Selge tjenester og varer innen brannsikring - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 364,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 364,000
Equity
NOK 744,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.5%
Very good
Equity as a share of total capital

Who owns VBM BRANNSIKRING AS?

VBM BYGGFORNYELSE AS
VBM BRANNSIKRING AS
NOK 6.2m rev. · NOK 364,000 profit

VBM BRANNSIKRING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VBM BRANNSIKRING AS

Who owns VBM BRANNSIKRING AS?

VBM BYGGFORNYELSE AS is the largest registered owner, with 60.0%.

What is the revenue of VBM BRANNSIKRING AS?

VBM BRANNSIKRING AS had revenue of NOK 6.2m in 2025.

Who is the general manager of VBM BRANNSIKRING AS?

Simen Endre Johnsen is registered as general manager of VBM BRANNSIKRING AS.

Where is VBM BRANNSIKRING AS based?

VBM BRANNSIKRING AS has its business address in Billingstad.

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.