BIZTRAC BETA
Uoppgitt

AM TANGSTAD HOLDING AS

Org. no. 930255432 Limited company (AS) Steinkjer Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −114,000
Equity NOK 3.0m
Incorporated 2022
Share capital NOK 37,000

Signals

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

AM TANGSTAD HOLDING AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 930255432. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 37,000, divided into 25 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −114,000
Equity
NOK 3.0m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns AM TANGSTAD HOLDING AS?

ARE MORTEN TANGSTAD
AM TANGSTAD HOLDING AS
· NOK −114,000 profit

AM TANGSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AM TANGSTAD HOLDING AS own?

AM TANGSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AM TANGSTAD HOLDING AS

Who owns AM TANGSTAD HOLDING AS?

ARE MORTEN TANGSTAD is the largest registered owner, with 100.0%.

Who is the general manager of AM TANGSTAD HOLDING AS?

Are Morten Tangstad is registered as general manager of AM TANGSTAD HOLDING AS.

Where is AM TANGSTAD HOLDING AS based?

AM TANGSTAD HOLDING AS has its business address in Follafoss.

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.