biztrac. BETA
COMPANY REGISTER PROFILE
935648599 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

BALESTRAND TECHNOLOGIES AS

Org. no. 935648599 Limited company (AS) Høyanger Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −300
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−300 kr).

BALESTRAND TECHNOLOGIES AS is registered as a limited company in Høyanger, Vestland with organisation number 935648599. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, produksjon og salg av mekaniske og teknologiske løsninger til industri- og anleggsbransjen, samt tilhørende konsulenttjenester og annen virksomhet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −300
Equity
NOK 30,000
Est. value
NOK 48,000

Financial health · 2025

Liquidity
100.04
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BALESTRAND TECHNOLOGIES AS?

BALESTRAND TECHNOLOGIES AS
· NOK −300 profit

BALESTRAND TECHNOLOGIES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BALESTRAND TECHNOLOGIES AS

Who owns BALESTRAND TECHNOLOGIES AS?

E25 HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of BALESTRAND TECHNOLOGIES AS?

Sondre Eraker Eivindsen is registered as general manager of BALESTRAND TECHNOLOGIES AS.

Where is BALESTRAND TECHNOLOGIES AS based?

BALESTRAND TECHNOLOGIES AS has its business address in Nessane.

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.