BIZTRAC BETA
Business and other management consultancy activities

TRONDHEIM ENGINEERING AS

Org. no. 913176073 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 19.1m
Operating profit NOK 1.6m
Equity NOK 1.8m
Incorporated 2014
Employees 18
Share capital NOK 130,000

TRONDHEIM ENGINEERING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913176073. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014 and has 18 registered employees. Registered share capital is NOK 130,000, divided into 1300 shares. The company's stated purpose is: “Drive industri, handel,transport,erverve og forstå drift av eiendom og annen næringsvirksomhet som herved står i forbindelse så som kjøp/salg av aksjer, utleie driftstilbehør, verktøy, konteinere, maskiner og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 19.1m
Operating profit
NOK 1.6m
Equity
NOK 1.8m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns TRONDHEIM ENGINEERING AS?

TRENG KAPITAL AS
TRONDHEIM ENGINEERING AS
NOK 19.1m rev. · NOK 1.6m profit

TRONDHEIM ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONDHEIM ENGINEERING AS

Who owns TRONDHEIM ENGINEERING AS?

TRENG KAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of TRONDHEIM ENGINEERING AS?

TRONDHEIM ENGINEERING AS had revenue of NOK 19.1m in 2025.

Where is TRONDHEIM ENGINEERING AS based?

TRONDHEIM ENGINEERING AS has its business address in Heimdal.

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.