BIZTRAC BETA
Rental and operating of own or leased real estate

GEN2 JELSA AS

Org. no. 914388244 Limited company (AS) Horten Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 17.8m
Operating profit NOK 17.7m
Equity NOK 5.8m
Incorporated 2014
Share capital NOK 100,000

Signals

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

GEN2 JELSA AS is registered as a limited company in Horten, Vestfold with organisation number 914388244. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å investere i, utvikle, eie og drifte eiendom og produksjonsanlegg for hydrogen, samt rådgivning og investeringer knyttet til aktiviteter som bidrar til å skape sirkulærøkonomi rundt disse aktivitetene. Og alt som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.8m in revenue and NOK 17.7m in operating profit.

Key figures · 2024

Revenue
NOK 17.8m
Operating profit
NOK 17.7m
Equity
NOK 5.8m
Est. value
NOK 37.5m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.8%
Good
Equity as a share of total capital

Who owns GEN2 JELSA AS?

GEN2 ENERGY AS
GEN2 JELSA AS
NOK 17.8m rev. · NOK 17.7m profit

GEN2 JELSA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEN2 JELSA AS

Who owns GEN2 JELSA AS?

GEN2 ENERGY AS is the largest registered owner, with 100.0%.

What is the revenue of GEN2 JELSA AS?

GEN2 JELSA AS had revenue of NOK 17.8m in 2024.

Where is GEN2 JELSA AS based?

GEN2 JELSA AS has its business address in Borre.

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.