BIZTRAC BETA
Uoppgitt

PROVENY HOLDING AS

Org. no. 931180088 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

PROVENY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931180088. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer i aksjer og andeler og andre produkter/tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessant i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.0%
Weak
Equity as a share of total capital

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

Who owns PROVENY HOLDING AS?

TOM FREDRIK HAUGEN
PROVENY HOLDING AS
NOK 0 rev. · NOK 0 profit

PROVENY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROVENY HOLDING AS

Who owns PROVENY HOLDING AS?

TOM FREDRIK HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of PROVENY HOLDING AS?

PROVENY HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of PROVENY HOLDING AS?

Tom Fredrik Haugen is registered as general manager of PROVENY HOLDING AS.

Where is PROVENY HOLDING AS based?

PROVENY HOLDING AS has its business address in Oslo.

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.