BIZTRAC BETA
Other business support service activities n.e.c.

DATATRYKK TRONDHEIM AS

Org. no. 935043565 Limited company (AS) Trondheim Incorporated 1984 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 6.7m
Incorporated 1984
Share capital NOK 3.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

DATATRYKK TRONDHEIM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935043565. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 1984. Registered share capital is NOK 3.0m, divided into 15500 shares. The company's stated purpose is: “Forvaltning og kjøp og salg av aksjer og andre verdipapirer og eiendom, samt virksomhet i tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −29,000
Equity
NOK 6.7m
Est. value
NOK 13.3m

Financial health · 2024

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

Who owns DATATRYKK TRONDHEIM AS?

PER KRISTIAN STUBBAN
DATATRYKK TRONDHEIM AS
· NOK −29,000 profit

DATATRYKK TRONDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DATATRYKK TRONDHEIM AS own?

DATATRYKK TRONDHEIM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about DATATRYKK TRONDHEIM AS

Who owns DATATRYKK TRONDHEIM AS?

PER KRISTIAN STUBBAN is the largest registered owner, with 100.0%.

Who is the general manager of DATATRYKK TRONDHEIM AS?

Per Kristian Stubban is registered as general manager of DATATRYKK TRONDHEIM AS.

Where is DATATRYKK TRONDHEIM AS based?

DATATRYKK TRONDHEIM 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.