BIZTRAC BETA
Rental and operating of own or leased real estate

SYN OG HØRSELSENTERET AS

Org. no. 934166051 Limited company (AS) Gjesdal Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 377,000
Operating profit NOK 212,000
Equity NOK 2.0m
Incorporated 1983
Share capital NOK 145,000

SYN OG HØRSELSENTERET AS is registered as a limited company in Gjesdal, Rogaland with organisation number 934166051. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1983. Registered share capital is NOK 145,000, divided into 85 shares. The company's stated purpose is: “Å gjøre seg interessert i fast eiendom gjennom kjøp, utleie og leie samt fremleie, og forskjelligartet tjenesteytelse til andre nærings- utøvere, samt å gjøre seg interessert i andre økonomiske foretagener gjennom interessent-aksje- innskudd o.l.”. The most recent filed accounts, for the 2024 financial year, show NOK 377,000 in revenue and NOK 212,000 in operating profit.

Key figures · 2024

Revenue
NOK 377,000
Operating profit
NOK 212,000
Equity
NOK 2.0m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.3%
Very good
Equity as a share of total capital

Who owns SYN OG HØRSELSENTERET AS?

REIN AS
SYN OG HØRSELSENTERET AS
NOK 377,000 rev. · NOK 212,000 profit

SYN OG HØRSELSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYN OG HØRSELSENTERET AS

Who owns SYN OG HØRSELSENTERET AS?

REIN AS is the largest registered owner, with 100.0%.

What is the revenue of SYN OG HØRSELSENTERET AS?

SYN OG HØRSELSENTERET AS had revenue of NOK 377,000 in 2024.

Where is SYN OG HØRSELSENTERET AS based?

SYN OG HØRSELSENTERET AS has its business address in Ålgård.

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.