BIZTRAC BETA
Operation of sports facilities

AARTSELAAR HOLDING AS

Org. no. 928796450 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 393,000
Incorporated 2022
Share capital NOK 33,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Nylig endring 2026-07-04 Adresseendring registrert 2026-07-04.

AARTSELAAR HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 928796450. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2022. Registered share capital is NOK 33,000, divided into 30 shares. The company's stated purpose is: “Eie av fingertunge aktiviteter med mye venga.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 393,000
Est. value
NOK 608,000

Financial health · 2025

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

Who owns AARTSELAAR HOLDING AS?

STEVEN VAN DIJCK
AARTSELAAR HOLDING AS
NOK 0 rev. · NOK −10,000 profit

AARTSELAAR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AARTSELAAR HOLDING AS own?

AARTSELAAR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AARTSELAAR HOLDING AS

Who owns AARTSELAAR HOLDING AS?

STEVEN VAN DIJCK is the largest registered owner, with 100.0%.

What is the revenue of AARTSELAAR HOLDING AS?

AARTSELAAR HOLDING AS had revenue of NOK 0 in 2025.

Where is AARTSELAAR HOLDING AS based?

AARTSELAAR HOLDING AS has its business address in Tromsø.

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.