BIZTRAC BETA
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

LINDLAND PUKK AS

Org. no. 986734465 Limited company (AS) Lyngdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 27.6m
Operating profit NOK 29,000
Equity NOK 5.9m
Incorporated 2004
Share capital NOK 740,000

LINDLAND PUKK AS is registered as a limited company in Lyngdal, Agder with organisation number 986734465. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 2004. Registered share capital is NOK 740,000, divided into 1000 shares. The company's stated purpose is: “Bergvirksomhet herunder knusing av masser, samt annen virksomhet som naturlig faller inn under dette. Selskapet kan også eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.6m in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 27.6m
Operating profit
NOK 29,000
Equity
NOK 5.9m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.4%
Very good
Equity as a share of total capital

Who owns LINDLAND PUKK AS?

LINDLAND PERFORMANCE 2 AS
LINDLAND PUKK AS
NOK 27.6m rev. · NOK 29,000 profit

LINDLAND PUKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINDLAND PUKK AS

Who owns LINDLAND PUKK AS?

LINDLAND PERFORMANCE 2 AS is the largest registered owner, with 100.0%.

What is the revenue of LINDLAND PUKK AS?

LINDLAND PUKK AS had revenue of NOK 27.6m in 2024.

Who is the general manager of LINDLAND PUKK AS?

Roar Lindland is registered as general manager of LINDLAND PUKK AS.

Where is LINDLAND PUKK AS based?

LINDLAND PUKK AS has its business address in Lyngdal.

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.