BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

SPIDER CONSULT AS

Org. no. 926836714 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 175,000
Operating profit NOK 141,000
Equity NOK 214,000
Incorporated 2021
Share capital NOK 30,000

SPIDER CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 926836714. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Manager for modellvirksomhet. Fotografivirksomhet. Rådgivning til strategi og forretningsutvikling. Foredragsvirksomhet. Mindre investeringer i Norske AS.”. The most recent filed accounts, for the 2025 financial year, show NOK 175,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 175,000
Operating profit
NOK 141,000
Equity
NOK 214,000
Est. value
NOK 552,000

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.0%
Good
Equity as a share of total capital

Who owns SPIDER CONSULT AS?

ANGELA HAUAN-ZAMORA
SPIDER CONSULT AS
NOK 175,000 rev. · NOK 141,000 profit

SPIDER CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPIDER CONSULT AS own?

SPIDER CONSULT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPIDER CONSULT AS

Who owns SPIDER CONSULT AS?

ANGELA HAUAN-ZAMORA is the largest registered owner, with 100.0%.

What is the revenue of SPIDER CONSULT AS?

SPIDER CONSULT AS had revenue of NOK 175,000 in 2025.

Where is SPIDER CONSULT AS based?

SPIDER CONSULT AS has its business address in Oslo.

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.