BIZTRAC BETA
Buying and selling of own real estate

NORDSTAD HOLDING AS

Org. no. 995481502 Limited company (AS) Tynset Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK 3.9m
Incorporated 2010
Share capital NOK 100,000

Signals

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

NORDSTAD HOLDING AS is registered as a limited company in Tynset, Innlandet with organisation number 995481502. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er investering i andre selskaper samt annen type virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 3.9m
Est. value
NOK 9.9m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.2%
Good
Equity as a share of total capital

Who owns NORDSTAD HOLDING AS?

JAKOB NORDSTAD
NORDSTAD HOLDING AS
NOK 0 rev. · NOK −30,000 profit

NORDSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORDSTAD HOLDING AS own?

NORDSTAD HOLDING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about NORDSTAD HOLDING AS

Who owns NORDSTAD HOLDING AS?

JAKOB NORDSTAD is the largest registered owner, with 100.0%.

What is the revenue of NORDSTAD HOLDING AS?

NORDSTAD HOLDING AS had revenue of NOK 0 in 2024.

Where is NORDSTAD HOLDING AS based?

NORDSTAD HOLDING AS has its business address in Tynset.

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.