biztrac. BETA
COMPANY REGISTER PROFILE
913883039 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other personal service activities n.e.c.

ENERGETIC RELEASE AS

Org. no. 913883039 Limited company (AS) Hemsedal Incorporated 2014 Active
Revenue 2025 NOK 381,000
Operating profit NOK 33,000
Equity NOK 327,000
Incorporated 2014
Share capital NOK 30,000

ENERGETIC RELEASE AS is registered as a limited company in Hemsedal, Buskerud with organisation number 913883039. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Yte konsulenttjenester, energiarbeid, bevissthetskursing, kjøp, salg og utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 381,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 381,000
▼ −43 %
Operating profit
NOK 33,000
▼ −90 %
Equity
NOK 327,000
▲ +9 %
Est. value
NOK 468,000

Financial health · 2025

Liquidity
1.92
Good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
50.9%
Very good
Equity as a share of total capital

Who owns ENERGETIC RELEASE AS?

ENERGETIC RELEASE AS
NOK 381,000 rev. · NOK 33,000 profit

ENERGETIC RELEASE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENERGETIC RELEASE AS

Who owns ENERGETIC RELEASE AS?

Inge Joar Holsen is the largest registered owner, with 100.0%.

What is the revenue of ENERGETIC RELEASE AS?

ENERGETIC RELEASE AS had revenue of NOK 381,000 in 2025.

Who is the general manager of ENERGETIC RELEASE AS?

Inge Joar Holsen is registered as general manager of ENERGETIC RELEASE AS.

Where is ENERGETIC RELEASE AS based?

ENERGETIC RELEASE AS has its business address in Hemsedal.

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.