BIZTRAC BETA
Buying and selling of own real estate

T-M-T HOLDING AS

Org. no. 933627950 Limited company (AS) Østre Toten Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).

T-M-T HOLDING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 933627950. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 23,000
Est. value
NOK 21,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns T-M-T HOLDING AS?

RUNE TORSTEINSHAUGEN
T-M-T HOLDING AS
· NOK −1,000 profit

T-M-T HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does T-M-T HOLDING AS own?

T-M-T HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about T-M-T HOLDING AS

Who owns T-M-T HOLDING AS?

RUNE TORSTEINSHAUGEN is the largest registered owner, with 100.0%.

Who is the general manager of T-M-T HOLDING AS?

Rune Torsteinshaugen is registered as general manager of T-M-T HOLDING AS.

Where is T-M-T HOLDING AS based?

T-M-T HOLDING AS has its business address in Kolbu.

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.