BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

TSM DRIFT AS

Org. no. 921700040 Limited company (AS) Ringebu Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 252,000
Equity NOK −642,000
Incorporated 2018
Share capital NOK 1.6m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−642k kr).

TSM DRIFT AS is registered as a limited company in Ringebu, Innlandet with organisation number 921700040. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2018. Registered share capital is NOK 1.6m, divided into 16030 shares. The company's stated purpose is: “Butikk med salg av kjøkkeninnredning og utstyr og annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 252,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 252,000
Equity
NOK −642,000
Est. value
NOK 1.9m

Financial health · 2025

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

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

Who owns TSM DRIFT AS?

SINDRE MYHRSVEEN HOLDING AS
TSM DRIFT AS
NOK 5.6m rev. · NOK 252,000 profit

TSM DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TSM DRIFT AS

Who owns TSM DRIFT AS?

SINDRE MYHRSVEEN HOLDING AS is the largest registered owner, with 92.2%.

What is the revenue of TSM DRIFT AS?

TSM DRIFT AS had revenue of NOK 5.6m in 2025.

Who is the general manager of TSM DRIFT AS?

Terje Amundsen is registered as general manager of TSM DRIFT AS.

Where is TSM DRIFT AS based?

TSM DRIFT AS has its business address in Fåvang.

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.