BIZTRAC BETA
Wholesale of other machinery and equipment

VULKEN FIRESERVICE AS

Org. no. 832906492 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 12.8m
Operating profit NOK 2.6m
Equity NOK 2.4m
Incorporated 2024
Employees 7
Share capital NOK 200,000

VULKEN FIRESERVICE AS is registered as a limited company in Stavanger, Rogaland with organisation number 832906492. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Selskapets virksomhet er salg og sertifisering av brannvernutstyr, samt annen beslektet næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.8m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 12.8m
Operating profit
NOK 2.6m
Equity
NOK 2.4m
Est. value
NOK 9.5m

Financial health · 2025

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

Who owns VULKEN FIRESERVICE AS?

VULKEN MARITIM AS
VULKEN FIRESERVICE AS
NOK 12.8m rev. · NOK 2.6m profit

VULKEN FIRESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VULKEN FIRESERVICE AS

Who owns VULKEN FIRESERVICE AS?

VULKEN MARITIM AS is the largest registered owner, with 80.0%.

What is the revenue of VULKEN FIRESERVICE AS?

VULKEN FIRESERVICE AS had revenue of NOK 12.8m in 2025.

Who is the general manager of VULKEN FIRESERVICE AS?

Morten Gabrielsen is registered as general manager of VULKEN FIRESERVICE AS.

Where is VULKEN FIRESERVICE AS based?

VULKEN FIRESERVICE AS has its business address in Stavanger.

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.