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

ENOCO ITB AS

Org. no. 914977282 Limited company (AS) Stjørdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 10.0m
Operating profit NOK 2.9m
Equity NOK 226,000
Incorporated 2015
Employees 11
Share capital NOK 40,000

ENOCO ITB AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 914977282. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2015 and has 11 registered employees. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Levere løsninger innen byggautomasjon og energiøkonomisering til totalentreprenører og større byggherrer.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.0m in revenue and NOK 2.9m in operating profit.

Former names: PROCO AS

Key figures · 2025

Revenue
NOK 10.0m
▼ −23 %
Operating profit
NOK 2.9m
▼ −63 %
Equity
NOK 226,000
▲ +4 %
Est. value
NOK 12.3m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
29.8%
Very good
Return on total assets
Solidity
2.3%
Not satisfactory
Equity as a share of total capital

Who owns ENOCO ITB AS?

ENOCO ITB AS
NOK 10.0m rev. · NOK 2.9m profit

ENOCO ITB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENOCO ITB AS

Who owns ENOCO ITB AS?

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

What is the revenue of ENOCO ITB AS?

ENOCO ITB AS had revenue of NOK 10.0m in 2025.

Who is the general manager of ENOCO ITB AS?

Henrik Myhre is registered as general manager of ENOCO ITB AS.

Where is ENOCO ITB AS based?

ENOCO ITB 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.