BIZTRAC BETA
Other captive investment companies

TORE WADAHL AS

Org. no. 989018779 Limited company (AS) Sør-Fron Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 2.0m
Incorporated 2005
Share capital NOK 400,000

Signals

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

TORE WADAHL AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 989018779. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 1 shares. The company's stated purpose is: “Eie, drive, utvikle og investere i fast eiendom, verdipapirer og andre formuesobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 2.0m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns TORE WADAHL AS?

TORE WADAHL
TORE WADAHL AS
NOK 0 rev. · NOK −13,000 profit

TORE WADAHL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORE WADAHL AS own?

TORE WADAHL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TORE WADAHL AS

Who owns TORE WADAHL AS?

TORE WADAHL is the largest registered owner, with 100.0%.

What is the revenue of TORE WADAHL AS?

TORE WADAHL AS had revenue of NOK 0 in 2025.

Who is the general manager of TORE WADAHL AS?

Tore Wadahl is registered as general manager of TORE WADAHL AS.

Where is TORE WADAHL AS based?

TORE WADAHL AS has its business address in Gålå.

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.