BIZTRAC BETA
Rental and operating of own or leased real estate

ABELI ENERGI AS

Org. no. 915514219 Limited company (AS) Flekkefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 157,000
Operating profit NOK −658,000
Equity NOK 1.0m
Incorporated 2015
Share capital NOK 30,000

Signals

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

ABELI ENERGI AS is registered as a limited company in Flekkefjord, Agder with organisation number 915514219. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Drive med produksjon av energi samt eierskap i andre selskap som produserer eller foredler energi.”. The most recent filed accounts, for the 2025 financial year, show NOK 157,000 in revenue and NOK −658,000 in operating profit.

Key figures · 2025

Revenue
NOK 157,000
Operating profit
NOK −658,000
Equity
NOK 1.0m
Est. value
NOK 948,000

Financial health · 2025

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

Who owns ABELI ENERGI AS?

ABELI HOLDING AS
ABELI ENERGI AS
NOK 157,000 rev. · NOK −658,000 profit

ABELI ENERGI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ABELI ENERGI AS

Who owns ABELI ENERGI AS?

ABELI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ABELI ENERGI AS?

ABELI ENERGI AS had revenue of NOK 157,000 in 2025.

Who is the general manager of ABELI ENERGI AS?

Rune Reinertsen is registered as general manager of ABELI ENERGI AS.

Where is ABELI ENERGI AS based?

ABELI ENERGI AS has its business address in Flekkefjord.

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.