BIZTRAC BETA
Electrical installation

BALESTRAND ELEKTRO AS

Org. no. 998551617 Limited company (AS) Sogndal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 955,000
Operating profit NOK 316,000
Equity NOK 3.8m
Incorporated 2012
Share capital NOK 100,000

BALESTRAND ELEKTRO AS is registered as a limited company in Sogndal, Vestland with organisation number 998551617. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Sal av elektrotenester, installasjonsverksemd, samt sal av tilhøyrande varer. Selskapet kan og delta som aksjonær, eller på anna måte engasjere seg i andre føretak uansett føremål og selskapsform.”. The most recent filed accounts, for the 2024 financial year, show NOK 955,000 in revenue and NOK 316,000 in operating profit.

Key figures · 2024

Revenue
NOK 955,000
Operating profit
NOK 316,000
Equity
NOK 3.8m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns BALESTRAND ELEKTRO AS?

KNUT THORSNES
BALESTRAND ELEKTRO AS
NOK 955,000 rev. · NOK 316,000 profit

BALESTRAND ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BALESTRAND ELEKTRO AS

Who owns BALESTRAND ELEKTRO AS?

KNUT THORSNES is the largest registered owner, with 100.0%.

What is the revenue of BALESTRAND ELEKTRO AS?

BALESTRAND ELEKTRO AS had revenue of NOK 955,000 in 2024.

Who is the general manager of BALESTRAND ELEKTRO AS?

Knut Thorsnes is registered as general manager of BALESTRAND ELEKTRO AS.

Where is BALESTRAND ELEKTRO AS based?

BALESTRAND ELEKTRO AS has its business address in Balestrand.

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.