BIZTRAC BETA
Other captive investment companies

NYTRØ HOLDING AS

Org. no. 921675364 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK −49,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−49k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

NYTRØ HOLDING AS is registered as a limited company in Bodø, Nordland with organisation number 921675364. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forvalte og investere i aksjer i andre selskaper, drift av andre selskaper og investering i fast eiendom konsulentvirksomhet innen 3D print teknologi og annet som naturlig faller sammen med dette.”.

Key figures · 2024

Operating profit
NOK −30,000
Equity
NOK −49,000

Financial health · 2024

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

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

Who owns NYTRØ HOLDING AS?

EIRIK NYTRØ
NYTRØ HOLDING AS
· NOK −30,000 profit

NYTRØ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NYTRØ HOLDING AS own?

NYTRØ HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NYTRØ HOLDING AS

Who owns NYTRØ HOLDING AS?

EIRIK NYTRØ is the largest registered owner, with 100.0%.

Who is the general manager of NYTRØ HOLDING AS?

Eirik Nytrø is registered as general manager of NYTRØ HOLDING AS.

Where is NYTRØ HOLDING AS based?

NYTRØ HOLDING AS has its business address in Bodø.

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.