BIZTRAC BETA
Rental and operating of own or leased real estate

SPC INVEST AS

Org. no. 988877492 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 13,000
Operating profit NOK −169,000
Equity NOK 9.2m
Incorporated 2005
Share capital NOK 100,000

Signals

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

SPC INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 988877492. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i andre selskaper eller virksomheter, herunder å eie, forvalte og utleie av fast eiendom, samt å yte konsulenttjenester forbundet med hovedformålet.”. The most recent filed accounts, for the 2024 financial year, show NOK 13,000 in revenue and NOK −169,000 in operating profit.

Key figures · 2024

Revenue
NOK 13,000
Operating profit
NOK −169,000
Equity
NOK 9.2m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns SPC INVEST AS?

PER ANDREAS SVEUM
SPC INVEST AS
NOK 13,000 rev. · NOK −169,000 profit

SPC INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPC INVEST AS own?

SPC INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SPC INVEST AS

Who owns SPC INVEST AS?

PER ANDREAS SVEUM is the largest registered owner, with 100.0%.

What is the revenue of SPC INVEST AS?

SPC INVEST AS had revenue of NOK 13,000 in 2024.

Where is SPC INVEST AS based?

SPC INVEST 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.