BIZTRAC BETA
Other unspecified social services without accommodation

HØRSEL-SENTERET AS

Org. no. 984781377 Limited company (AS) Elverum Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 738,000
Equity NOK 238,000
Incorporated 2002
Share capital NOK 100,000

HØRSEL-SENTERET AS is registered as a limited company in Elverum, Innlandet with organisation number 984781377. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forretningsvirksomhet innen service og oppfølging overfor hørselshemmede, herunder deltagelse i andre selskaper samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 738,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 738,000
Equity
NOK 238,000
Est. value
NOK 2.6m

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns HØRSEL-SENTERET AS?

HEGE ØSTGAARD HORTEN
HØRSEL-SENTERET AS
NOK 3.1m rev. · NOK 738,000 profit

HØRSEL-SENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØRSEL-SENTERET AS

Who owns HØRSEL-SENTERET AS?

HEGE ØSTGAARD HORTEN is the largest registered owner, with 100.0%.

What is the revenue of HØRSEL-SENTERET AS?

HØRSEL-SENTERET AS had revenue of NOK 3.1m in 2024.

Who is the general manager of HØRSEL-SENTERET AS?

Hege Østgaard Horten is registered as general manager of HØRSEL-SENTERET AS.

Where is HØRSEL-SENTERET AS based?

HØRSEL-SENTERET AS has its business address in Elverum.

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.