BIZTRAC BETA
Other personal service activities n.e.c.

STIKKAN HOLDING AS

Org. no. 991958886 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −27,000
Equity NOK 5.9m
Incorporated 2007
Share capital NOK 200,000

Signals

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

STIKKAN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 991958886. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drive virksomhet innenfor konsulenttjenester, investering og deltakelse i andre selskaper, samt virksomhet forbundet med dette. Selskapet kan eie fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK 5.9m
Est. value
NOK 7.9m

Financial health · 2025

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

Who owns STIKKAN HOLDING AS?

STIG FURUSETH
STIKKAN HOLDING AS
NOK 0 rev. · NOK −27,000 profit

STIKKAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIKKAN HOLDING AS own?

STIKKAN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIKKAN HOLDING AS

Who owns STIKKAN HOLDING AS?

STIG FURUSETH is the largest registered owner, with 100.0%.

What is the revenue of STIKKAN HOLDING AS?

STIKKAN HOLDING AS had revenue of NOK 0 in 2024.

Where is STIKKAN HOLDING AS based?

STIKKAN HOLDING 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.