BIZTRAC BETA
Activities of excursion and event organisers

SPIDER NETWORK AS

Org. no. 927119978 Limited company (AS) Ullensaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −48,000
Equity NOK 10,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−48k kr).

SPIDER NETWORK AS is registered as a limited company in Ullensaker, Akershus with organisation number 927119978. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Golfarrangement og b2b aktiviteter for næringslivet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −48,000
Equity
NOK 10,000
Est. value
NOK 14,000

Financial health · 2024

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

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

Who owns SPIDER NETWORK AS?

CHRISTIAN BOGSTAD LØVSTAD
SPIDER NETWORK AS
NOK 0 rev. · NOK −48,000 profit

SPIDER NETWORK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPIDER NETWORK AS

Who owns SPIDER NETWORK AS?

CHRISTIAN BOGSTAD LØVSTAD is the largest registered owner, with 33.3%.

What is the revenue of SPIDER NETWORK AS?

SPIDER NETWORK AS had revenue of NOK 0 in 2024.

Who is the general manager of SPIDER NETWORK AS?

Christian Bogstad Løvstad is registered as general manager of SPIDER NETWORK AS.

Where is SPIDER NETWORK AS based?

SPIDER NETWORK AS has its business address in Kløfta.

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.