BIZTRAC BETA
Technical testing and analysis

VIKEN BRANNSIKKERHET AS

Org. no. 925748641 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 95,000
Equity NOK 473,000
Incorporated 2020
Share capital NOK 30,000

VIKEN BRANNSIKKERHET AS is registered as a limited company in Frogn, Akershus with organisation number 925748641. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Driver virksomhet innen service og kontroll av brannslukkere og brannslukking. Selskapet driver også kursvirksomhet og nettsalg innenfor samme produkter. Selskapet skal også utføre service og vedlikehold av nødlys.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 95,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 95,000
Equity
NOK 473,000
Est. value
NOK 588,000

Financial health · 2025

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

Who owns VIKEN BRANNSIKKERHET AS?

ANTE HUSEBY
VIKEN BRANNSIKKERHET AS
NOK 1.4m rev. · NOK 95,000 profit

VIKEN BRANNSIKKERHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKEN BRANNSIKKERHET AS

Who owns VIKEN BRANNSIKKERHET AS?

ANTE HUSEBY is the largest registered owner, with 100.0%.

What is the revenue of VIKEN BRANNSIKKERHET AS?

VIKEN BRANNSIKKERHET AS had revenue of NOK 1.4m in 2025.

Who is the general manager of VIKEN BRANNSIKKERHET AS?

Ante Huseby is registered as general manager of VIKEN BRANNSIKKERHET AS.

Where is VIKEN BRANNSIKKERHET AS based?

VIKEN BRANNSIKKERHET AS has its business address in Drøbak.

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.