BIZTRAC BETA
Machining of metals

TST TRONDHEIM SKJÆRETEKNIKK AS

Org. no. 914726794 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 722,000
Operating profit NOK 158,000
Equity NOK 341,000
Incorporated 2014
Share capital NOK 30,000

TST TRONDHEIM SKJÆRETEKNIKK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914726794. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å utføre tjenester innen bearbeiding av metaller, utvikle dataverktøy og maskiner for bearbeiding av metaller, samt relaterte områder, samt deltakelse i selskaper som arbeider innen tilknyttede områder.”. The most recent filed accounts, for the 2025 financial year, show NOK 722,000 in revenue and NOK 158,000 in operating profit.

Key figures · 2025

Revenue
NOK 722,000
Operating profit
NOK 158,000
Equity
NOK 341,000
Est. value
NOK 681,000

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.6%
Very good
Equity as a share of total capital

Who owns TST TRONDHEIM SKJÆRETEKNIKK AS?

JBA INVEST AS
TST TRONDHEIM SKJÆRETEKNIKK AS
NOK 722,000 rev. · NOK 158,000 profit

TST TRONDHEIM SKJÆRETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TST TRONDHEIM SKJÆRETEKNIKK AS

Who owns TST TRONDHEIM SKJÆRETEKNIKK AS?

JBA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TST TRONDHEIM SKJÆRETEKNIKK AS?

TST TRONDHEIM SKJÆRETEKNIKK AS had revenue of NOK 722,000 in 2025.

Where is TST TRONDHEIM SKJÆRETEKNIKK AS based?

TST TRONDHEIM SKJÆRETEKNIKK AS has its business address in Trondheim.

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.