BIZTRAC BETA
Rental and operating of own or leased real estate

VATNEEIDET BUTIKKEIENDOM AS

Org. no. 994819003 Limited company (AS) Haram Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.3m
Equity NOK 7.2m
Incorporated 2009
Share capital NOK 900,000

Signals

1 flags
  • Nylig endring 2026-06-19 Adresseendring registrert 2026-06-19.

VATNEEIDET BUTIKKEIENDOM AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 994819003. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Eie og leie ut fast eiendom , samt alt som står i forbndelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.3m
Equity
NOK 7.2m
Est. value
NOK 7.8m

Financial health · 2024

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
66.3%
Very good
Equity as a share of total capital

Who owns VATNEEIDET BUTIKKEIENDOM AS?

H.I. GIØRTZ HOLDING AS
VATNEEIDET BUTIKKEIENDOM AS
NOK 1.8m rev. · NOK 1.3m profit

VATNEEIDET BUTIKKEIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VATNEEIDET BUTIKKEIENDOM AS

Who owns VATNEEIDET BUTIKKEIENDOM AS?

H.I. GIØRTZ HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VATNEEIDET BUTIKKEIENDOM AS?

VATNEEIDET BUTIKKEIENDOM AS had revenue of NOK 1.8m in 2024.

Where is VATNEEIDET BUTIKKEIENDOM AS based?

VATNEEIDET BUTIKKEIENDOM AS has its business address in Brattvåg.

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.