BIZTRAC BETA
Other captive investment companies

HÅVARD VINGELEN AS

Org. no. 917529485 Limited company (AS) Midtre Gauldal Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 3.8m
Incorporated 2016
Share capital NOK 85,000

Signals

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

HÅVARD VINGELEN AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 917529485. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 85,000, divided into 35 shares. The company's stated purpose is: “Å eie og forvalte eierandeler, herunder aksjer, i andre selskaper og alt som direkte eller indirekte står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 3.8m
Est. value
NOK 10.1m

Financial health · 2024

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

Who owns HÅVARD VINGELEN AS?

HÅVARD VINGELEN
HÅVARD VINGELEN AS
NOK 0 rev. · NOK −9,000 profit

HÅVARD VINGELEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HÅVARD VINGELEN AS own?

HÅVARD VINGELEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HÅVARD VINGELEN AS

Who owns HÅVARD VINGELEN AS?

HÅVARD VINGELEN is the largest registered owner, with 100.0%.

What is the revenue of HÅVARD VINGELEN AS?

HÅVARD VINGELEN AS had revenue of NOK 0 in 2024.

Where is HÅVARD VINGELEN AS based?

HÅVARD VINGELEN AS has its business address in Soknedal.

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.