BIZTRAC BETA
Uoppgitt

BLIX WERNER HOLDING AS

Org. no. 929077822 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 1.3m
Equity NOK 1.9m
Incorporated 2022
Share capital NOK 30,000

BLIX WERNER HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 929077822. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kontrollere og administrere datterselskap og andre selskap det eies aksjer og andeler i.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 1.3m
Equity
NOK 1.9m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns BLIX WERNER HOLDING AS?

ERIK NICOLAY BLIX WERNER
BLIX WERNER HOLDING AS
NOK 1.4m rev. · NOK 1.3m profit

BLIX WERNER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLIX WERNER HOLDING AS own?

BLIX WERNER HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BLIX WERNER HOLDING AS

Who owns BLIX WERNER HOLDING AS?

ERIK NICOLAY BLIX WERNER is the largest registered owner, with 100.0%.

What is the revenue of BLIX WERNER HOLDING AS?

BLIX WERNER HOLDING AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BLIX WERNER HOLDING AS?

Erik Nicolay Blix Werner is registered as general manager of BLIX WERNER HOLDING AS.

Where is BLIX WERNER HOLDING AS based?

BLIX WERNER HOLDING 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.