BIZTRAC BETA
Site preparation

LERFALDET GRAVESERVICE AS

Org. no. 927429799 Limited company (AS) Hole Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 316,000
Operating profit NOK −11,000
Equity NOK 906,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

LERFALDET GRAVESERVICE AS is registered as a limited company in Hole, Buskerud with organisation number 927429799. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenør, bygg og anleggsleverandør.”. The most recent filed accounts, for the 2024 financial year, show NOK 316,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 316,000
Operating profit
NOK −11,000
Equity
NOK 906,000
Est. value
NOK 500,000

Financial health · 2024

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

Who owns LERFALDET GRAVESERVICE AS?

EMIL BIRGER LERFALDET
LERFALDET GRAVESERVICE AS
NOK 316,000 rev. · NOK −11,000 profit

LERFALDET GRAVESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERFALDET GRAVESERVICE AS

Who owns LERFALDET GRAVESERVICE AS?

EMIL BIRGER LERFALDET is the largest registered owner, with 100.0%.

What is the revenue of LERFALDET GRAVESERVICE AS?

LERFALDET GRAVESERVICE AS had revenue of NOK 316,000 in 2024.

Who is the general manager of LERFALDET GRAVESERVICE AS?

Emil Birger Lerfaldet is registered as general manager of LERFALDET GRAVESERVICE AS.

Where is LERFALDET GRAVESERVICE AS based?

LERFALDET GRAVESERVICE AS has its business address in Sollihøgda.

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.