BIZTRAC BETA
Rental and operating of own or leased real estate

HOVDESVINGEN EIENDOM AS

Org. no. 913023471 Limited company (AS) Austevoll Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.8m
Equity NOK 4.4m
Incorporated 2013
Share capital NOK 450,000

Signals

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

HOVDESVINGEN EIENDOM AS is registered as a limited company in Austevoll, Vestland with organisation number 913023471. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Å kjøpe, eie og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.8m
Equity
NOK 4.4m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
26.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.0%
Weak
Equity as a share of total capital

Who owns HOVDESVINGEN EIENDOM AS?

BIRKELAND GRUPPEN AS
HOVDESVINGEN EIENDOM AS
NOK 3.1m rev. · NOK 1.8m profit

HOVDESVINGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVDESVINGEN EIENDOM AS

Who owns HOVDESVINGEN EIENDOM AS?

BIRKELAND GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of HOVDESVINGEN EIENDOM AS?

HOVDESVINGEN EIENDOM AS had revenue of NOK 3.1m in 2024.

Where is HOVDESVINGEN EIENDOM AS based?

HOVDESVINGEN EIENDOM AS has its business address in Storebø.

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.