biztrac. BETA
COMPANY REGISTER PROFILE
913424735 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

KAPITALSPIRE AS

Org. no. 913424735 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 83,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

KAPITALSPIRE AS is registered as a limited company in Oslo, Oslo with organisation number 913424735. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å bedrive investering i verdipapirer, eiendom og andre investeringer samt yte konsulenttjenester og andre tjenester/produkter som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −12,000
▼ −111 %
Equity
NOK 83,000
▲ +123 %
Est. value
NOK 211,000

Financial health · 2025

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

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

Who owns KAPITALSPIRE AS?

KAPITALSPIRE AS
· NOK −12,000 profit

KAPITALSPIRE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAPITALSPIRE AS own?

KAPITALSPIRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KAPITALSPIRE AS

Who owns KAPITALSPIRE AS?

Geir Eirik Jacobsen is the largest registered owner, with 100.0%.

Who is the general manager of KAPITALSPIRE AS?

Geir Eirik Jacobsen is registered as general manager of KAPITALSPIRE AS.

Where is KAPITALSPIRE AS based?

KAPITALSPIRE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.