BIZTRAC BETA
Research and experimental development on natural sciences and engineering

ENOCO AS

Org. no. 880452452 Limited company (AS) Stjørdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 14.8m
Operating profit NOK −486,000
Equity NOK 5.2m
Incorporated 1998
Employees 12
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−486k kr).

ENOCO AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 880452452. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 1998 and has 12 registered employees. Registered share capital is NOK 300,000, divided into 30000000 shares. The company's stated purpose is: “Selskapets leveranse av elektrotekniske installasjoner over hele Norge. Annen forskning og annet utviklingsarbeid innen naturvitenskap og teknikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.8m in revenue and NOK −486,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.8m
Operating profit
NOK −486,000
Equity
NOK 5.2m
Est. value
NOK 18.1m

Financial health · 2024

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.3%
Good
Equity as a share of total capital

Who owns ENOCO AS?

PROMAX AS
ENOCO AS
NOK 14.8m rev. · NOK −486,000 profit

ENOCO AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENOCO AS

Who owns ENOCO AS?

PROMAX AS is the largest registered owner, with 90.5%.

What is the revenue of ENOCO AS?

ENOCO AS had revenue of NOK 14.8m in 2024.

Who is the general manager of ENOCO AS?

Ulf Roar Aakenes is registered as general manager of ENOCO AS.

Where is ENOCO AS based?

ENOCO AS has its business address in Stjørdal.

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.