BIZTRAC BETA
Wholesale of information and communication equipment

HØR AS

Org. no. 816563712 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 30.2m
Operating profit NOK −2.7m
Equity NOK −3.6m
Incorporated 2016
Employees 18
Share capital NOK 400,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,7 mill kr).

HØR AS is registered as a limited company in Oslo, Oslo with organisation number 816563712. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2016 and has 18 registered employees. Registered share capital is NOK 400,000, divided into 200000 shares. The company's stated purpose is: “Selskapets virksomhet er etablering av driftsdestinasjoner og driftskonsept for HØR Studio.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.2m in revenue and NOK −2.7m in operating profit.

Key figures · 2024

Revenue
NOK 30.2m
Operating profit
NOK −2.7m
Equity
NOK −3.6m

Financial health · 2024

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

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

Who owns HØR AS?

HEAR IT AS
HØR AS
NOK 30.2m rev. · NOK −2.7m profit

HØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØR AS

Who owns HØR AS?

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

What is the revenue of HØR AS?

HØR AS had revenue of NOK 30.2m in 2024.

Who is the general manager of HØR AS?

Janne Hallset Mykkelbost is registered as general manager of HØR AS.

Where is HØR AS based?

HØR 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.