BIZTRAC BETA
Other captive investment companies

VANDELAY INDUSTRIES AS

Org. no. 988642339 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −46,000
Equity NOK 28.3m
Incorporated 2005
Share capital NOK 50,000

Signals

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

VANDELAY INDUSTRIES AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988642339. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Å eie aksjer, fast eiendom eller på annen måte engasjere seg i næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 28.3m
Est. value
NOK 25.8m

Financial health · 2024

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

Who owns VANDELAY INDUSTRIES AS?

FRODE MIDJO
VANDELAY INDUSTRIES AS
NOK 0 rev. · NOK −46,000 profit

VANDELAY INDUSTRIES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VANDELAY INDUSTRIES AS own?

VANDELAY INDUSTRIES AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VANDELAY INDUSTRIES AS

Who owns VANDELAY INDUSTRIES AS?

FRODE MIDJO is the largest registered owner, with 100.0%.

What is the revenue of VANDELAY INDUSTRIES AS?

VANDELAY INDUSTRIES AS had revenue of NOK 0 in 2024.

Where is VANDELAY INDUSTRIES AS based?

VANDELAY INDUSTRIES 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.