biztrac. BETA
COMPANY REGISTER PROFILE
918843094 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

INCHOATE AS

Org. no. 918843094 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK 55,000
Equity NOK 1.6m
Incorporated 2017
Share capital NOK 30,000

INCHOATE AS is registered as a limited company in Oslo, Oslo with organisation number 918843094. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Primært investering i aksjer. Sekundært konsulentvirksomhet innen strategi og forretningsutvikling og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK 55,000
▲ +441 %
Equity
NOK 1.6m
▼ −11 %
Est. value
NOK 966,000

Financial health · 2025

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

Who owns INCHOATE AS?

INCHOATE AS
NOK 100,000 rev. · NOK 55,000 profit

INCHOATE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INCHOATE AS own?

INCHOATE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about INCHOATE AS

Who owns INCHOATE AS?

Heiki Andre Strengelsrud is the largest registered owner, with 100.0%.

What is the revenue of INCHOATE AS?

INCHOATE AS had revenue of NOK 100,000 in 2025.

Who is the general manager of INCHOATE AS?

Heiki Andre Strengelsrud is registered as general manager of INCHOATE AS.

Where is INCHOATE AS based?

INCHOATE 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.