BIZTRAC BETA
Retail sale of medical and orthopaedic goods

VERKLAND HOLDING AS

Org. no. 918926348 Limited company (AS) Malvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −51,000
Equity NOK 3.6m
Incorporated 2017
Share capital NOK 140,000

Signals

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

VERKLAND HOLDING AS is registered as a limited company in Malvik, Trøndelag with organisation number 918926348. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2017. Registered share capital is NOK 140,000, divided into 100 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskaper, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −51,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −51,000
Equity
NOK 3.6m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns VERKLAND HOLDING AS?

ANNY NESSE VERKLAND
VERKLAND HOLDING AS
NOK 0 rev. · NOK −51,000 profit

VERKLAND HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VERKLAND HOLDING AS own?

VERKLAND HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about VERKLAND HOLDING AS

Who owns VERKLAND HOLDING AS?

ANNY NESSE VERKLAND is the largest registered owner, with 50.0%.

What is the revenue of VERKLAND HOLDING AS?

VERKLAND HOLDING AS had revenue of NOK 0 in 2024.

Where is VERKLAND HOLDING AS based?

VERKLAND HOLDING AS has its business address in Vikhammer.

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.