biztrac. BETA
COMPANY REGISTER PROFILE
935796598 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of other civil engineering projects n.e.c.

GEITFJELL VIND DA

Org. no. 935796598 General partnership with shared liability (DA) Hamar Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2.7m
Equity NOK −924,000
Incorporated 2025

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−924k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,7 mill kr).

GEITFJELL VIND DA is registered as a general partnership with shared liability in Hamar, Innlandet with organisation number 935796598. The business is classified under construction of other civil engineering projects n.e.c. (NACE 42.990). The company was incorporated in 2025. The company's stated purpose is: “Utvikle, bygge, eie, drifte og vedlikeholde landbaserte vindparker med tilhørende virksomhet, direkte eller gjennom eierskap i selskaper med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2.7m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2.7m
Equity
NOK −924,000

Financial health · 2025

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

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

Who owns GEITFJELL VIND DA?

No shareholders are registered for GEITFJELL VIND DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GEITFJELL VIND DA

What is the revenue of GEITFJELL VIND DA?

GEITFJELL VIND DA had revenue of NOK 0 in 2025.

Where is GEITFJELL VIND DA based?

GEITFJELL VIND DA has its business address in Hamar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.