BIZTRAC BETA
Uoppgitt

INPROCESS INVEST AS

Org. no. 922167761 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −110,000
Equity NOK 8.3m
Incorporated 2019
Share capital NOK 30,000

Signals

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

INPROCESS INVEST AS is registered as a limited company in Asker, Akershus with organisation number 922167761. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsbransjen: aktiv og varig investering i aksjer og andre verdipapir samt aktiv forvaltning av egne midler og investeringer i eiendom og andre liknende varige aktiva.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −110,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −110,000
Equity
NOK 8.3m
Est. value
NOK 28.7m

Financial health · 2024

Liquidity
-1357.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.2%
Very good
Equity as a share of total capital

Who owns INPROCESS INVEST AS?

STEINAR MOLDE
INPROCESS INVEST AS
NOK 0 rev. · NOK −110,000 profit

INPROCESS INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does INPROCESS INVEST AS own?

INPROCESS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INPROCESS INVEST AS

Who owns INPROCESS INVEST AS?

STEINAR MOLDE is the largest registered owner, with 80.0%.

What is the revenue of INPROCESS INVEST AS?

INPROCESS INVEST AS had revenue of NOK 0 in 2024.

Where is INPROCESS INVEST AS based?

INPROCESS INVEST AS has its business address in Asker.

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.