BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

BRANNKONSULENTENE AS

Org. no. 918423613 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 20,000
Incorporated 2017
Share capital NOK 30,000

BRANNKONSULENTENE AS is registered as a limited company in Oslo, Oslo with organisation number 918423613. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med brannteknisk rådgivning, opplæring og øvelser, samt det som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 20,000
Est. value
NOK 32,000

Financial health · 2024

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

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

Who owns BRANNKONSULENTENE AS?

KJELL ARMAND THUNE
BRANNKONSULENTENE AS
NOK 0 rev. · NOK 0 profit

BRANNKONSULENTENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRANNKONSULENTENE AS

Who owns BRANNKONSULENTENE AS?

KJELL ARMAND THUNE is the largest registered owner, with 100.0%.

What is the revenue of BRANNKONSULENTENE AS?

BRANNKONSULENTENE AS had revenue of NOK 0 in 2024.

Who is the general manager of BRANNKONSULENTENE AS?

Kjell Armand Thune is registered as general manager of BRANNKONSULENTENE AS.

Where is BRANNKONSULENTENE AS based?

BRANNKONSULENTENE AS has its business address in Oslo.

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.