BIZTRAC BETA
Business and other management consultancy activities

EAH COGNITO AS

Org. no. 836011732 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −752
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−752 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-08-07.

EAH COGNITO AS is registered as a limited company in Stavanger, Rogaland with organisation number 836011732. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivning, konsulenttjenester og styrearbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −752 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −752
Equity
NOK 22,000
Est. value
NOK 35,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns EAH COGNITO AS?

IDAR ANDREAS HILLERSØY
EAH COGNITO AS
NOK 0 rev. · NOK −752 profit

EAH COGNITO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EAH COGNITO AS

Who owns EAH COGNITO AS?

IDAR ANDREAS HILLERSØY is the largest registered owner, with 100.0%.

What is the revenue of EAH COGNITO AS?

EAH COGNITO AS had revenue of NOK 0 in 2025.

Who is the general manager of EAH COGNITO AS?

Idar Andreas Hillersøy is registered as general manager of EAH COGNITO AS.

Where is EAH COGNITO AS based?

EAH COGNITO 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.