BIZTRAC BETA
Technical testing and analysis

KTN STM HOLDING AS

Org. no. 916653468 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 1.4m
Incorporated 2016
Share capital NOK 750,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KTN STM HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 916653468. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2016. Registered share capital is NOK 750,000, divided into 10000 shares. The company's stated purpose is: “Eie og forvalte aksjer og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper og hva som står i forbindelse hermed.”.

Key figures · 2024

Operating profit
NOK −22,000
Equity
NOK 1.4m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns KTN STM HOLDING AS?

STM INSPEKSJON HOLDING AS
KTN STM HOLDING AS
· NOK −22,000 profit

KTN STM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KTN STM HOLDING AS own?

KTN STM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KTN STM HOLDING AS

Who owns KTN STM HOLDING AS?

STM INSPEKSJON HOLDING AS is the largest registered owner, with 90.0%.

Who is the general manager of KTN STM HOLDING AS?

Håvard Mjanger is registered as general manager of KTN STM HOLDING AS.

Where is KTN STM HOLDING AS based?

KTN STM HOLDING AS has its business address in Laksevåg.

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.