BIZTRAC BETA
Uoppgitt

FEVANG ENERGY HOLDING AS

Org. no. 930195227 Limited company (AS) Nes Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 11,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

FEVANG ENERGY HOLDING AS is registered as a limited company in Nes, Akershus with organisation number 930195227. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2024

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

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

Who owns FEVANG ENERGY HOLDING AS?

GEIR FEVANG
FEVANG ENERGY HOLDING AS
· NOK −6,000 profit

FEVANG ENERGY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FEVANG ENERGY HOLDING AS own?

FEVANG ENERGY HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FEVANG ENERGY HOLDING AS

Who owns FEVANG ENERGY HOLDING AS?

GEIR FEVANG is the largest registered owner, with 100.0%.

Who is the general manager of FEVANG ENERGY HOLDING AS?

Geir Fevang is registered as general manager of FEVANG ENERGY HOLDING AS.

Where is FEVANG ENERGY HOLDING AS based?

FEVANG ENERGY HOLDING AS has its business address in Hvam.

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.