biztrac. BETA
COMPANY REGISTER PROFILE
992991291 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of other builders' carpentry and joinery

NYSTUEN HOLDING AS

Org. no. 992991291 Limited company (AS) Østre Toten Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −87,000
Equity NOK 12.7m
Incorporated 2008
Share capital NOK 258,000

Signals

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

NYSTUEN HOLDING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 992991291. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2008. Registered share capital is NOK 258,000, divided into 621 shares. The company's stated purpose is: “Investeringsvirksomhet samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −87,000
▲ +57 %
Equity
NOK 12.7m
▲ +10 %
Est. value
NOK 14.3m

Financial health · 2025

Liquidity
90.70
Very good
Current assets ÷ current liabilities
Profitability
6.5%
Satisfactory
Return on total assets
Solidity
81.6%
Very good
Equity as a share of total capital

Who owns NYSTUEN HOLDING AS?

NYSTUEN HOLDING AS
· NOK −87,000 profit

NYSTUEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NYSTUEN HOLDING AS own?

NYSTUEN HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about NYSTUEN HOLDING AS

Who owns NYSTUEN HOLDING AS?

Espen Nystuen Pettersen is the largest registered owner, with 100.0%.

Who is the general manager of NYSTUEN HOLDING AS?

Espen Nystuen Pettersen is registered as general manager of NYSTUEN HOLDING AS.

Where is NYSTUEN HOLDING AS based?

NYSTUEN HOLDING AS has its business address in Skreia.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.