BIZTRAC BETA
Other health services

HEAR IT AS

Org. no. 915596894 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK −1.6m
Equity NOK 6.4m
Incorporated 2015
Share capital NOK 1.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).
  • Nylig endring 2026-07-27 Aksjekapital registrert 2026-07-27.

HEAR IT AS is registered as a limited company in Oslo, Oslo with organisation number 915596894. The business is classified under other health services (NACE 86.993). The company was incorporated in 2015. Registered share capital is NOK 1.3m, divided into 134015 shares. The company's stated purpose is: “Å arbeide for «din viktigste sosiale sans - din hørsel», ved å utvikle innovasjon i hørselsomsorg.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK −1.6m
Equity
NOK 6.4m
Est. value
NOK 10.0m

Financial health · 2024

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.4%
Good
Equity as a share of total capital

Who owns HEAR IT AS?

RYTTER-JAGER INVEST AS
HEAR IT AS
NOK 4.2m rev. · NOK −1.6m profit

HEAR IT AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does HEAR IT AS own?

HEAR IT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HEAR IT AS

Who owns HEAR IT AS?

RYTTER-JAGER INVEST AS is the largest registered owner, with 17.5%.

What is the revenue of HEAR IT AS?

HEAR IT AS had revenue of NOK 4.2m in 2024.

Who is the general manager of HEAR IT AS?

Per Robert Jager is registered as general manager of HEAR IT AS.

Where is HEAR IT AS based?

HEAR IT 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.