BIZTRAC BETA
Other technical consultancy

HØYSPENT KONSULT AS

Org. no. 997970543 Limited company (AS) Nittedal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 1.3m
Equity NOK 47,000
Incorporated 2012
Share capital NOK 30,000

HØYSPENT KONSULT AS is registered as a limited company in Nittedal, Akershus with organisation number 997970543. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Teknisk rådgivning og konsulenttjenester til kraftbransjen, og andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 1.3m
Equity
NOK 47,000
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.5%
Weak
Equity as a share of total capital

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

Who owns HØYSPENT KONSULT AS?

KENNETH ANDRE OPSKAR
HØYSPENT KONSULT AS
NOK 3.8m rev. · NOK 1.3m profit

HØYSPENT KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØYSPENT KONSULT AS

Who owns HØYSPENT KONSULT AS?

KENNETH ANDRE OPSKAR is the largest registered owner, with 100.0%.

What is the revenue of HØYSPENT KONSULT AS?

HØYSPENT KONSULT AS had revenue of NOK 3.8m in 2025.

Who is the general manager of HØYSPENT KONSULT AS?

Kenneth Andre Opskar is registered as general manager of HØYSPENT KONSULT AS.

Where is HØYSPENT KONSULT AS based?

HØYSPENT KONSULT AS has its business address in Hagan.

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.