BIZTRAC BETA
Other tour operator activities

NOLIMITS HOLDING AS

Org. no. 922665761 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −17,000
Equity NOK 5,000
Incorporated 2019
Share capital NOK 80,000

Signals

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

NOLIMITS HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 922665761. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2019. Registered share capital is NOK 80,000, divided into 80000 shares. The company's stated purpose is: “Investere i aksjer og andre selskaper gjennom aksjekjøp.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −17,000
Equity
NOK 5,000
Est. value
NOK 8,000

Financial health · 2025

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

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

Who owns NOLIMITS HOLDING AS?

HARALD SANNARNES
NOLIMITS HOLDING AS
NOK 5,000 rev. · NOK −17,000 profit

NOLIMITS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOLIMITS HOLDING AS own?

NOLIMITS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOLIMITS HOLDING AS

Who owns NOLIMITS HOLDING AS?

HARALD SANNARNES is the largest registered owner, with 100.0%.

What is the revenue of NOLIMITS HOLDING AS?

NOLIMITS HOLDING AS had revenue of NOK 5,000 in 2025.

Where is NOLIMITS HOLDING AS based?

NOLIMITS HOLDING AS has its business address in Kristiansand S.

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.