biztrac. BETA
COMPANY REGISTER PROFILE
989119850 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

VERNANG HOLDING AS

Org. no. 989119850 Limited company (AS) Voss Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −73,000
Equity NOK −546,000
Incorporated 2005
Share capital NOK 759,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−546k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−73k kr).

VERNANG HOLDING AS is registered as a limited company in Voss, Vestland with organisation number 989119850. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2005. Registered share capital is NOK 759,000, divided into 110 shares. The company's stated purpose is: “Å eie aksjer og andeler i andre selskaper samt hva med dette hører til.”.

Key figures · 2025

Operating profit
NOK −73,000
▼ −1 %
Equity
NOK −546,000
▼ −11 %

Financial health · 2025

Liquidity
48.26
Very good
Current assets ÷ current liabilities
Profitability
-2.6%
Not satisfactory
Return on total assets
Solidity
-26.1%
Weak
Equity as a share of total capital

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

Who owns VERNANG HOLDING AS?

VERNANG HOLDING AS
· NOK −73,000 profit

VERNANG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VERNANG HOLDING AS own?

VERNANG HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VERNANG HOLDING AS

Who owns VERNANG HOLDING AS?

Tore Håkon Vernang is the largest registered owner, with 100.0%.

Who is the general manager of VERNANG HOLDING AS?

Tore Håkon Vernang is registered as general manager of VERNANG HOLDING AS.

Where is VERNANG HOLDING AS based?

VERNANG HOLDING AS has its business address in Vossestrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.