BIZTRAC BETA
Uoppgitt

KVELDRO HOLDING AS

Org. no. 925963402 Limited company (AS) Senja Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 5.5m
Incorporated 2020
Share capital NOK 30,000

Signals

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

KVELDRO HOLDING AS is registered as a limited company in Senja, Troms with organisation number 925963402. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og andre selskaper, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 5.5m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns KVELDRO HOLDING AS?

OLE JOHANNESSEN
KVELDRO HOLDING AS
NOK 0 rev. · NOK −18,000 profit

KVELDRO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVELDRO HOLDING AS own?

KVELDRO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KVELDRO HOLDING AS

Who owns KVELDRO HOLDING AS?

OLE JOHANNESSEN is the largest registered owner, with 100.0%.

What is the revenue of KVELDRO HOLDING AS?

KVELDRO HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of KVELDRO HOLDING AS?

Ole Johannessen is registered as general manager of KVELDRO HOLDING AS.

Where is KVELDRO HOLDING AS based?

KVELDRO HOLDING AS has its business address in Finnsnes.

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.