BIZTRAC BETA
Other technical consultancy

PROXIMA HYDROTECH AS

Org. no. 918808302 Limited company (AS) Kvinnherad Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 28.5m
Operating profit NOK 2.1m
Equity NOK 6.2m
Incorporated 2017
Employees 13
Share capital NOK 1.5m

PROXIMA HYDROTECH AS is registered as a limited company in Kvinnherad, Vestland with organisation number 918808302. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017 and has 13 registered employees. Registered share capital is NOK 1.5m, divided into 15000 shares. The company's stated purpose is: “Tenester knyttet til drift og vedlikehold av vannkraftverk samt annen virksomhet i tilknytning til denne, herunder deltakelse i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.5m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 28.5m
Operating profit
NOK 2.1m
Equity
NOK 6.2m
Est. value
NOK 13.8m

Financial health · 2024

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

Who owns PROXIMA HYDROTECH AS?

KAIA SOLUTIONS AS
PROXIMA HYDROTECH AS
NOK 28.5m rev. · NOK 2.1m profit

PROXIMA HYDROTECH AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROXIMA HYDROTECH AS

Who owns PROXIMA HYDROTECH AS?

KAIA SOLUTIONS AS is the largest registered owner, with 33.3%.

What is the revenue of PROXIMA HYDROTECH AS?

PROXIMA HYDROTECH AS had revenue of NOK 28.5m in 2024.

Who is the general manager of PROXIMA HYDROTECH AS?

Marianne Helvik is registered as general manager of PROXIMA HYDROTECH AS.

Where is PROXIMA HYDROTECH AS based?

PROXIMA HYDROTECH AS has its business address in Seimsfoss.

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.