BIZTRAC BETA
Rental and operating of own or leased real estate

HAAVIKA UTBYGGINGSSELSKAP AS

Org. no. 983036449 Limited company (AS) Frøya Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 801,000
Operating profit NOK 389,000
Equity NOK 1.4m
Incorporated 2001
Share capital NOK 4.8m

Signals

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

HAAVIKA UTBYGGINGSSELSKAP AS is registered as a limited company in Frøya, Trøndelag with organisation number 983036449. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 4.8m, divided into 3000 shares. The company's stated purpose is: “Utbygging og salg av eiendom i Haavika, Frøya kommune.”. The most recent filed accounts, for the 2024 financial year, show NOK 801,000 in revenue and NOK 389,000 in operating profit.

Key figures · 2024

Revenue
NOK 801,000
Operating profit
NOK 389,000
Equity
NOK 1.4m
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.6%
Satisfactory
Equity as a share of total capital

Who owns HAAVIKA UTBYGGINGSSELSKAP AS?

STEINARS HOLDING AS
HAAVIKA UTBYGGINGSSELSKAP AS
NOK 801,000 rev. · NOK 389,000 profit

HAAVIKA UTBYGGINGSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAAVIKA UTBYGGINGSSELSKAP AS

Who owns HAAVIKA UTBYGGINGSSELSKAP AS?

STEINARS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAAVIKA UTBYGGINGSSELSKAP AS?

HAAVIKA UTBYGGINGSSELSKAP AS had revenue of NOK 801,000 in 2024.

Where is HAAVIKA UTBYGGINGSSELSKAP AS based?

HAAVIKA UTBYGGINGSSELSKAP AS has its business address in Kverva.

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.