BIZTRAC BETA
Architectural activities

HAGA & GROV AS SIVILARKITEKTER MNAL

Org. no. 963275676 Limited company (AS) Stavanger Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 406,000
Equity NOK 4.2m
Incorporated 1992
Share capital NOK 250,000

HAGA & GROV AS SIVILARKITEKTER MNAL is registered as a limited company in Stavanger, Rogaland with organisation number 963275676. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1992. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Drift av arkitektkontor.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 406,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 406,000
Equity
NOK 4.2m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns HAGA & GROV AS SIVILARKITEKTER MNAL?

HILDE DAGNY HAGA
HAGA & GROV AS SIVILARKITEKTER MNAL
NOK 3.8m rev. · NOK 406,000 profit

HAGA & GROV AS SIVILARKITEKTER MNAL has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAGA & GROV AS SIVILARKITEKTER MNAL

Who owns HAGA & GROV AS SIVILARKITEKTER MNAL?

HILDE DAGNY HAGA is the largest registered owner, with 50.0%.

What is the revenue of HAGA & GROV AS SIVILARKITEKTER MNAL?

HAGA & GROV AS SIVILARKITEKTER MNAL had revenue of NOK 3.8m in 2024.

Who is the general manager of HAGA & GROV AS SIVILARKITEKTER MNAL?

Rune Grov is registered as general manager of HAGA & GROV AS SIVILARKITEKTER MNAL.

Where is HAGA & GROV AS SIVILARKITEKTER MNAL based?

HAGA & GROV AS SIVILARKITEKTER MNAL has its business address in Stavanger.

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.