BIZTRAC BETA
Rental and operating of own or leased real estate

HOFSETH AQUA PROPERTY AS

Org. no. 931385097 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 89.3m
Operating profit NOK 50.2m
Equity NOK 235.2m
Incorporated 2023
Share capital NOK 642,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HOFSETH AQUA PROPERTY AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931385097. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 642,000, divided into 30000 shares. The company's stated purpose is: “Investering i og utleie av næringseiendom, herunder investering i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 89.3m in revenue and NOK 50.2m in operating profit.

Key figures · 2024

Revenue
NOK 89.3m
Operating profit
NOK 50.2m
Equity
NOK 235.2m
Est. value
NOK 241.9m

Financial health · 2024

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

Who owns HOFSETH AQUA PROPERTY AS?

HIYR AS
HOFSETH AQUA PROPERTY AS
NOK 89.3m rev. · NOK 50.2m profit

HOFSETH AQUA PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOFSETH AQUA PROPERTY AS

Who owns HOFSETH AQUA PROPERTY AS?

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

What is the revenue of HOFSETH AQUA PROPERTY AS?

HOFSETH AQUA PROPERTY AS had revenue of NOK 89.3m in 2024.

Where is HOFSETH AQUA PROPERTY AS based?

HOFSETH AQUA PROPERTY AS has its business address in Ålesund.

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.