BIZTRAC BETA
Site preparation

A. L GRAVETEKNIKK AS

Org. no. 931236512 Limited company (AS) Brønnøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 545,000
Equity NOK 1.2m
Incorporated 2023
Share capital NOK 240,000

Signals

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

A. L GRAVETEKNIKK AS is registered as a limited company in Brønnøy, Nordland with organisation number 931236512. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 240,000, divided into 30 shares. The company's stated purpose is: “Anleggsvirksomhet og brøyting samt beslektet virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 545,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 545,000
Equity
NOK 1.2m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns A. L GRAVETEKNIKK AS?

A. LANDE HOLDING AS
A. L GRAVETEKNIKK AS
NOK 6.3m rev. · NOK 545,000 profit

A. L GRAVETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A. L GRAVETEKNIKK AS

Who owns A. L GRAVETEKNIKK AS?

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

What is the revenue of A. L GRAVETEKNIKK AS?

A. L GRAVETEKNIKK AS had revenue of NOK 6.3m in 2025.

Who is the general manager of A. L GRAVETEKNIKK AS?

André Lande is registered as general manager of A. L GRAVETEKNIKK AS.

Where is A. L GRAVETEKNIKK AS based?

A. L GRAVETEKNIKK AS has its business address in Velfjord.

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.