biztrac. BETA
COMPANY REGISTER PROFILE
916535228 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Technical testing and analysis

STM INSPEKSJON HOLDING AS

Org. no. 916535228 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 912,000
Incorporated 2015
Share capital NOK 45,000

Signals

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

STM INSPEKSJON HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 916535228. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2015. Registered share capital is NOK 45,000, divided into 30000 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 · 2025

Operating profit
NOK −9,000
▲ +61 %
Equity
NOK 912,000
▼ −9 %
Est. value
NOK 24.6m

Financial health · 2025

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

Who owns STM INSPEKSJON HOLDING AS?

STM INSPEKSJON HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STM INSPEKSJON HOLDING AS own?

STM INSPEKSJON HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STM INSPEKSJON HOLDING AS

Who owns STM INSPEKSJON HOLDING AS?

STM MASKINERING AS is the largest registered owner, with 25.0%.

Where is STM INSPEKSJON HOLDING AS based?

STM INSPEKSJON 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 03.10.2026.

Report a problem

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