BIZTRAC BETA
Uoppgitt

WEDØYA HOLDING AS

Org. no. 928681874 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK −1,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

WEDØYA HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928681874. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Forvaltning av eierinteresser og utøve virksomhet 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 −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −1,000

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.0%
Weak
Equity as a share of total capital

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

Who owns WEDØYA HOLDING AS?

KIM OMAR JOHANSEN
WEDØYA HOLDING AS
NOK 0 rev. · NOK −18,000 profit

WEDØYA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WEDØYA HOLDING AS own?

WEDØYA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WEDØYA HOLDING AS

Who owns WEDØYA HOLDING AS?

KIM OMAR JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of WEDØYA HOLDING AS?

WEDØYA HOLDING AS had revenue of NOK 0 in 2024.

Where is WEDØYA HOLDING AS based?

WEDØYA HOLDING AS has its business address in Trondheim.

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.