BIZTRAC BETA
Computer programming activities

ARISHOLM HOLDING AS

Org. no. 927075903 Limited company (AS) Nordre Follo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −131,000
Equity NOK 9.1m
Incorporated 2021
Share capital NOK 125,000

Signals

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

ARISHOLM HOLDING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 927075903. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 125,000, divided into 2100 shares. The company's stated purpose is: “Investering i aksjer og andre selskaper og virksomheter, deltakelse i virksomheter, samt naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −131,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −131,000
Equity
NOK 9.1m
Est. value
NOK 34.7m

Financial health · 2025

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

Who owns ARISHOLM HOLDING AS?

ERIK ARISHOLM
ARISHOLM HOLDING AS
NOK 0 rev. · NOK −131,000 profit

ARISHOLM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARISHOLM HOLDING AS own?

ARISHOLM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ARISHOLM HOLDING AS

Who owns ARISHOLM HOLDING AS?

ERIK ARISHOLM is the largest registered owner, with 100.0%.

What is the revenue of ARISHOLM HOLDING AS?

ARISHOLM HOLDING AS had revenue of NOK 0 in 2025.

Where is ARISHOLM HOLDING AS based?

ARISHOLM HOLDING AS has its business address in Tårnåsen.

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.