BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

LAUVDAL TECHNOLOGY AS

Org. no. 971512261 Limited company (AS) Lindesnes Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 400,000
Operating profit NOK 126,000
Equity NOK 31,000
Incorporated 1994
Share capital NOK 100,000

LAUVDAL TECHNOLOGY AS is registered as a limited company in Lindesnes, Agder with organisation number 971512261. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive virksomhet innen handel, produktutvikling og produksjon hovedsakelig basert på primærnæringene i inn- og utland, markedsføring, konsulentarbeide samt utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 400,000 in revenue and NOK 126,000 in operating profit.

Key figures · 2025

Revenue
NOK 400,000
Operating profit
NOK 126,000
Equity
NOK 31,000
Est. value
NOK 413,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LAUVDAL TECHNOLOGY AS?

DONOVAN NORDIC AS
LAUVDAL TECHNOLOGY AS
NOK 400,000 rev. · NOK 126,000 profit

LAUVDAL TECHNOLOGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUVDAL TECHNOLOGY AS

Who owns LAUVDAL TECHNOLOGY AS?

DONOVAN NORDIC AS is the largest registered owner, with 100.0%.

What is the revenue of LAUVDAL TECHNOLOGY AS?

LAUVDAL TECHNOLOGY AS had revenue of NOK 400,000 in 2025.

Where is LAUVDAL TECHNOLOGY AS based?

LAUVDAL TECHNOLOGY AS has its business address in Marnardal.

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.