biztrac. BETA
COMPANY REGISTER PROFILE
933086674 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

LERBERG GRAVESERVICE AS

Org. no. 933086674 Limited company (AS) Hol Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 1.2m
Equity NOK 1.6m
Incorporated 2024
Share capital NOK 30,000

LERBERG GRAVESERVICE AS is registered as a limited company in Hol, Buskerud with organisation number 933086674. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Graving, transport, snørydding og annen entreprenørvirksomhet. Kjøp og salg av varer innenfor bransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
▲ +34 %
Operating profit
NOK 1.2m
▲ +10 %
Equity
NOK 1.6m
▲ +101 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
24.7%
Very good
Return on total assets
Solidity
30.8%
Good
Equity as a share of total capital

Who owns LERBERG GRAVESERVICE AS?

LERBERG GRAVESERVICE AS
NOK 6.1m rev. · NOK 1.2m profit

LERBERG GRAVESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LERBERG GRAVESERVICE AS

Who owns LERBERG GRAVESERVICE AS?

Sigvart Lerberg is the largest registered owner, with 80.0%.

What is the revenue of LERBERG GRAVESERVICE AS?

LERBERG GRAVESERVICE AS had revenue of NOK 6.1m in 2025.

Who is the general manager of LERBERG GRAVESERVICE AS?

Sigvart Lerberg is registered as general manager of LERBERG GRAVESERVICE AS.

Where is LERBERG GRAVESERVICE AS based?

LERBERG GRAVESERVICE AS has its business address in Geilo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.