BIZTRAC BETA
Manufacture of engines and turbines, except aircraft, vehicle and cycle engines

VINDHJULFABRIKKEN AS

Org. no. 929976339 Limited company (AS) Gjøvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 75,000
Operating profit NOK −25,000
Equity NOK 14,000
Incorporated 2022
Share capital NOK 50,000

Signals

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

VINDHJULFABRIKKEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 929976339. The business is classified under manufacture of engines and turbines, except aircraft, vehicle and cycle engines (NACE 28.110). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Hovedoppgave er utvikling av miljøteknologi innen fornybar energi.”. The most recent filed accounts, for the 2025 financial year, show NOK 75,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 75,000
Operating profit
NOK −25,000
Equity
NOK 14,000
Est. value
NOK 47,000

Financial health · 2024

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

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

Who owns VINDHJULFABRIKKEN AS?

IDE OG PRODUKT AS
VINDHJULFABRIKKEN AS
NOK 75,000 rev. · NOK −25,000 profit

VINDHJULFABRIKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VINDHJULFABRIKKEN AS

Who owns VINDHJULFABRIKKEN AS?

IDE OG PRODUKT AS is the largest registered owner, with 70.0%.

What is the revenue of VINDHJULFABRIKKEN AS?

VINDHJULFABRIKKEN AS had revenue of NOK 75,000 in 2025.

Where is VINDHJULFABRIKKEN AS based?

VINDHJULFABRIKKEN AS has its business address in Gjøvik.

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.