BIZTRAC BETA
Uoppgitt

WIE NONDAL HOLDING AS

Org. no. 930981435 Limited company (AS) Ullensvang Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 27,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

WIE NONDAL HOLDING AS is registered as a limited company in Ullensvang, Vestland with organisation number 930981435. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å være holdingselskap for eierens investeringer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 27,000
Est. value
NOK 31,000

Financial health · 2024

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

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

Who owns WIE NONDAL HOLDING AS?

THOMAS NIKOLAI SKEIE NONDAL
WIE NONDAL HOLDING AS
NOK 0 rev. · NOK −3,000 profit

WIE NONDAL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WIE NONDAL HOLDING AS own?

WIE NONDAL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WIE NONDAL HOLDING AS

Who owns WIE NONDAL HOLDING AS?

THOMAS NIKOLAI SKEIE NONDAL is the largest registered owner, with 100.0%.

What is the revenue of WIE NONDAL HOLDING AS?

WIE NONDAL HOLDING AS had revenue of NOK 0 in 2024.

Where is WIE NONDAL HOLDING AS based?

WIE NONDAL HOLDING AS has its business address in Odda.

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.