BIZTRAC BETA
Computer programming activities

NCR HOLDING AS

Org. no. 990750823 Limited company (AS) Grue Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK −239,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

NCR HOLDING AS is registered as a limited company in Grue, Innlandet with organisation number 990750823. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Som morselskap å forvalte sine eierinteresser i all investert virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK −239,000

Financial health · 2024

Liquidity
1354.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-18.7%
Weak
Equity as a share of total capital

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

Who owns NCR HOLDING AS?

NIELS CHRISTOPHER ROLSDORPH
NCR HOLDING AS
NOK 0 rev. · NOK −24,000 profit

NCR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NCR HOLDING AS own?

NCR HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about NCR HOLDING AS

Who owns NCR HOLDING AS?

NIELS CHRISTOPHER ROLSDORPH is the largest registered owner, with 100.0%.

What is the revenue of NCR HOLDING AS?

NCR HOLDING AS had revenue of NOK 0 in 2024.

Where is NCR HOLDING AS based?

NCR HOLDING AS has its business address in Kirkenær.

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.