BIZTRAC BETA
Electrical installation

STEINVIKAUNE HOLDING AS

Org. no. 918425616 Limited company (AS) Stjørdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −58,000
Equity NOK 894,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

STEINVIKAUNE HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 918425616. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer, samt hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −58,000
Equity
NOK 894,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns STEINVIKAUNE HOLDING AS?

HENRIK STEINVIKAUNE
STEINVIKAUNE HOLDING AS
NOK 0 rev. · NOK −58,000 profit

STEINVIKAUNE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEINVIKAUNE HOLDING AS own?

STEINVIKAUNE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about STEINVIKAUNE HOLDING AS

Who owns STEINVIKAUNE HOLDING AS?

HENRIK STEINVIKAUNE is the largest registered owner, with 100.0%.

What is the revenue of STEINVIKAUNE HOLDING AS?

STEINVIKAUNE HOLDING AS had revenue of NOK 0 in 2024.

Where is STEINVIKAUNE HOLDING AS based?

STEINVIKAUNE HOLDING AS has its business address in Hegra.

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.