BIZTRAC BETA
Site preparation

HAAVE GRAVESERVICE AS

Org. no. 921183143 Limited company (AS) Notodden Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 134,000
Equity NOK 873,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

HAAVE GRAVESERVICE AS is registered as a limited company in Notodden, Telemark with organisation number 921183143. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Alt innen grunnarbeid, drenering, støttemur, planering, vann og anlegg samt annen virksomhet i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 134,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 134,000
Equity
NOK 873,000
Est. value
NOK 660,000

Financial health · 2024

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

Who owns HAAVE GRAVESERVICE AS?

LEIF KRISTIAN HAAVE
HAAVE GRAVESERVICE AS
NOK 8.2m rev. · NOK 134,000 profit

HAAVE GRAVESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAAVE GRAVESERVICE AS

Who owns HAAVE GRAVESERVICE AS?

LEIF KRISTIAN HAAVE is the largest registered owner, with 100.0%.

What is the revenue of HAAVE GRAVESERVICE AS?

HAAVE GRAVESERVICE AS had revenue of NOK 8.2m in 2024.

Who is the general manager of HAAVE GRAVESERVICE AS?

Leif Kristian Haave is registered as general manager of HAAVE GRAVESERVICE AS.

Where is HAAVE GRAVESERVICE AS based?

HAAVE GRAVESERVICE AS has its business address in Notodden.

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.