BIZTRAC BETA
Other captive investment companies

CAPENORTH AS

Org. no. 925173282 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 64,000
Operating profit NOK −4,000
Equity NOK 8.4m
Incorporated 2020
Share capital NOK 30,000

Signals

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

CAPENORTH AS is registered as a limited company in Stavanger, Rogaland with organisation number 925173282. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie og investerer i aksjer samt å yte tjenester og service til oljenæringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 64,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 64,000
Operating profit
NOK −4,000
Equity
NOK 8.4m
Est. value
NOK 16.0m

Financial health · 2025

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

Who owns CAPENORTH AS?

GEIR MAGNE MO JOHNSEN
CAPENORTH AS
NOK 64,000 rev. · NOK −4,000 profit

CAPENORTH AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CAPENORTH AS own?

CAPENORTH AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CAPENORTH AS

Who owns CAPENORTH AS?

GEIR MAGNE MO JOHNSEN is the largest registered owner, with 60.0%.

What is the revenue of CAPENORTH AS?

CAPENORTH AS had revenue of NOK 64,000 in 2025.

Who is the general manager of CAPENORTH AS?

Geir Magne Mo Johnsen is registered as general manager of CAPENORTH AS.

Where is CAPENORTH AS based?

CAPENORTH AS has its business address in Stavanger.

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.