biztrac. BETA
COMPANY REGISTER PROFILE
896687662 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

A K J ENERGITEKNIK AKTIEBOLAG NUF

Org. no. 896687662 Norwegian division of foreign business enterprise (NUF) Active
Ownership graph ↗
Revenue 2025 SEK 306.9m
Operating profit SEK 23.3m
Equity SEK 57.6m

A K J ENERGITEKNIK AKTIEBOLAG NUF is registered as a norwegian division of foreign business enterprise with organisation number 896687662. The business is classified under electrical installation (NACE 43.210). The most recent filed accounts, for the 2025 financial year, show SEK 306.9m in revenue and SEK 23.3m in operating profit.

Former names: A K J ENERGITEKNIK NUF

This company reports in SEK. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Revenue
SEK 306.9m
▼ −4 %
Operating profit
SEK 23.3m
▲ +186 %
Equity
SEK 57.6m
▲ +24 %
Est. value
NOK 88.1m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
13.5%
Good
Return on total assets
Solidity
24.4%
Good
Equity as a share of total capital

Who owns A K J ENERGITEKNIK AKTIEBOLAG NUF?

No shareholders are registered for A K J ENERGITEKNIK AKTIEBOLAG NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about A K J ENERGITEKNIK AKTIEBOLAG NUF

What is the revenue of A K J ENERGITEKNIK AKTIEBOLAG NUF?

A K J ENERGITEKNIK AKTIEBOLAG NUF had revenue of SEK 306.9m in 2025.

Who is the general manager of A K J ENERGITEKNIK AKTIEBOLAG NUF?

Pär Gustav Jansson is registered as general manager of A K J ENERGITEKNIK AKTIEBOLAG NUF.

Where is A K J ENERGITEKNIK AKTIEBOLAG NUF based?

A K J ENERGITEKNIK AKTIEBOLAG NUF has its business address in 652 21 Karlstad.

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.