BIZTRAC BETA
Buying and selling of own real estate

VORPA HOLDING AS

Org. no. 911768364 Limited company (AS) Hitra Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 253,000
Operating profit NOK −181,000
Equity NOK 2.0m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−181k kr).

VORPA HOLDING AS is registered as a limited company in Hitra, Trøndelag with organisation number 911768364. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i og drift av fast eiendom, investeringer i verdipapirer, andre virksomheter og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 253,000 in revenue and NOK −181,000 in operating profit.

Key figures · 2025

Revenue
NOK 253,000
Operating profit
NOK −181,000
Equity
NOK 2.0m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns VORPA HOLDING AS?

RAGNAR VOLDEN
VORPA HOLDING AS
NOK 253,000 rev. · NOK −181,000 profit

VORPA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VORPA HOLDING AS own?

VORPA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VORPA HOLDING AS

Who owns VORPA HOLDING AS?

RAGNAR VOLDEN is the largest registered owner, with 100.0%.

What is the revenue of VORPA HOLDING AS?

VORPA HOLDING AS had revenue of NOK 253,000 in 2025.

Where is VORPA HOLDING AS based?

VORPA HOLDING AS has its business address in Hemnskjela.

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.