BIZTRAC BETA
Construction of residential and non-residential buildings

SP. HOLDING AS

Org. no. 997807952 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −90,000
Equity NOK 4.5m
Incorporated 2012
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−90k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SP. HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 997807952. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer, andre verdipapirer, eiendom og alt som naturlig hører til slik virksomhet.”.

Key figures · 2025

Operating profit
NOK −90,000
Equity
NOK 4.5m
Est. value
NOK 8.8m

Financial health · 2025

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

Who owns SP. HOLDING AS?

STIAN PERSSON
SP. HOLDING AS
· NOK −90,000 profit

SP. HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SP. HOLDING AS own?

SP. HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

SP. HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about SP. HOLDING AS

Who owns SP. HOLDING AS?

STIAN PERSSON is the largest registered owner, with 100.0%.

Who is the general manager of SP. HOLDING AS?

Stian Persson is registered as general manager of SP. HOLDING AS.

Where is SP. HOLDING AS based?

SP. HOLDING AS has its business address in Bjørøyhamn.

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.