BIZTRAC BETA
Warehousing and storage

NETSHOP HOLDING AS

Org. no. 929564081 Limited company (AS) Sandefjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 260,000
Operating profit NOK −613,000
Equity NOK 4.9m
Incorporated 2022
Share capital NOK 1.3m

Signals

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

NETSHOP HOLDING AS is registered as a limited company in Sandefjord, Vestfold with organisation number 929564081. The business is classified under warehousing and storage (NACE 52.100). The company was incorporated in 2022. Registered share capital is NOK 1.3m, divided into 1299999 shares. The company's stated purpose is: “Investering og deltakelse i andre virksomheter. Hovedkontortjenester: Utfører tjenester til eget konsern.”. The most recent filed accounts, for the 2025 financial year, show NOK 260,000 in revenue and NOK −613,000 in operating profit.

Key figures · 2025

Revenue
NOK 260,000
Operating profit
NOK −613,000
Equity
NOK 4.9m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns NETSHOP HOLDING AS?

LYSEBO HOLDING II AS
NETSHOP HOLDING AS
NOK 260,000 rev. · NOK −613,000 profit

NETSHOP HOLDING AS has 7 registered shareholders:

All shareholders and roles →

Which companies does NETSHOP HOLDING AS own?

NETSHOP HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about NETSHOP HOLDING AS

Who owns NETSHOP HOLDING AS?

LYSEBO HOLDING II AS is the largest registered owner, with 31.8%.

What is the revenue of NETSHOP HOLDING AS?

NETSHOP HOLDING AS had revenue of NOK 260,000 in 2025.

Where is NETSHOP HOLDING AS based?

NETSHOP HOLDING AS has its business address in Sandefjord.

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.