BIZTRAC BETA
Other technical consultancy

JAKHELLN BIOENERGI AS

Org. no. 994426133 Limited company (AS) Lillestrøm Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 771,000
Equity NOK 1.3m
Incorporated 2009
Share capital NOK 2.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JAKHELLN BIOENERGI AS is registered as a limited company in Lillestrøm, Akershus with organisation number 994426133. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2009. Registered share capital is NOK 2.1m, divided into 1 shares. The company's stated purpose is: “Drift og utvikling av bioenergi virksomhet, inkludert kjøp og salg av energi, og annet som er naturlig i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 771,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 771,000
Equity
NOK 1.3m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns JAKHELLN BIOENERGI AS?

JAKHELLN AS
JAKHELLN BIOENERGI AS
NOK 1.7m rev. · NOK 771,000 profit

JAKHELLN BIOENERGI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JAKHELLN BIOENERGI AS er morselskap for 2 datterselskaper:

Frequently asked questions about JAKHELLN BIOENERGI AS

Who owns JAKHELLN BIOENERGI AS?

JAKHELLN AS is the largest registered owner, with 100.0%.

What is the revenue of JAKHELLN BIOENERGI AS?

JAKHELLN BIOENERGI AS had revenue of NOK 1.7m in 2025.

Where is JAKHELLN BIOENERGI AS based?

JAKHELLN BIOENERGI AS has its business address in Lillestrøm.

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.