BIZTRAC BETA
Other captive investment companies

OLE JOHAN INVEST AS

Org. no. 912441334 Limited company (AS) Østre Toten Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −32,000
Equity NOK 1.3m
Incorporated 2013
Share capital NOK 30,000

Signals

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

OLE JOHAN INVEST AS is registered as a limited company in Østre Toten, Innlandet with organisation number 912441334. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og fond, og det som naturlig hører til dette, samt å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK 1.3m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns OLE JOHAN INVEST AS?

OLE JOHAN LINNERUD
OLE JOHAN INVEST AS
NOK 0 rev. · NOK −32,000 profit

OLE JOHAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLE JOHAN INVEST AS

Who owns OLE JOHAN INVEST AS?

OLE JOHAN LINNERUD is the largest registered owner, with 100.0%.

What is the revenue of OLE JOHAN INVEST AS?

OLE JOHAN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of OLE JOHAN INVEST AS?

Ole Johan Linnerud is registered as general manager of OLE JOHAN INVEST AS.

Where is OLE JOHAN INVEST AS based?

OLE JOHAN INVEST AS has its business address in Kapp.

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.