biztrac. BETA
COMPANY REGISTER PROFILE
923052003 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VETRHUS HOLDING AS

Org. no. 923052003 Limited company (AS) Flekkefjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 1.1m
Incorporated 2019
Share capital NOK 84,000

Signals

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

VETRHUS HOLDING AS is registered as a limited company in Flekkefjord, Agder with organisation number 923052003. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 84,000, divided into 6978 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
▼ −30 %
Equity
NOK 1.1m
▼ −1 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
43.1%
Very good
Equity as a share of total capital

Who owns VETRHUS HOLDING AS?

VETRHUS HOLDING AS
NOK 0 rev. · NOK −16,000 profit

VETRHUS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VETRHUS HOLDING AS own?

VETRHUS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VETRHUS HOLDING AS

Who owns VETRHUS HOLDING AS?

Torgny Vetrhus is the largest registered owner, with 100.0%.

What is the revenue of VETRHUS HOLDING AS?

VETRHUS HOLDING AS had revenue of NOK 0 in 2025.

Where is VETRHUS HOLDING AS based?

VETRHUS HOLDING AS has its business address in Flekkefjord.

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.