BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

HEAR IT B2B AS

Org. no. 816562112 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 46,000
Incorporated 2016
Share capital NOK 80,000

Signals

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

HEAR IT B2B AS is registered as a limited company in Oslo, Oslo with organisation number 816562112. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2016. Registered share capital is NOK 80,000, divided into 8000 shares. The company's stated purpose is: “Etablere forretningsvirksomhet innen lyd, hørsel og akustikk innenfor b2b-området. Herav ligger også design og utvikling av produkter og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 46,000
Est. value
NOK 57,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 HEAR IT B2B AS?

HEAR IT AS
HEAR IT B2B AS
NOK 0 rev. · NOK −6,000 profit

HEAR IT B2B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEAR IT B2B AS

Who owns HEAR IT B2B AS?

HEAR IT AS is the largest registered owner, with 100.0%.

What is the revenue of HEAR IT B2B AS?

HEAR IT B2B AS had revenue of NOK 0 in 2025.

Who is the general manager of HEAR IT B2B AS?

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

Where is HEAR IT B2B AS based?

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