BIZTRAC BETA
Site preparation

LINDELAND MASKIN AS

Org. no. 928517578 Limited company (AS) Sirdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK −1.4m
Equity NOK 31,000
Incorporated 2021
Employees 14
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

LINDELAND MASKIN AS is registered as a limited company in Sirdal, Agder with organisation number 928517578. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2021 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK −1.4m
Equity
NOK 31,000
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Weak
Equity as a share of total capital

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

Who owns LINDELAND MASKIN AS?

MARTIN LINDELAND
LINDELAND MASKIN AS
NOK 9.1m rev. · NOK −1.4m profit

LINDELAND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINDELAND MASKIN AS

Who owns LINDELAND MASKIN AS?

MARTIN LINDELAND is the largest registered owner, with 100.0%.

What is the revenue of LINDELAND MASKIN AS?

LINDELAND MASKIN AS had revenue of NOK 9.1m in 2024.

Who is the general manager of LINDELAND MASKIN AS?

Martin Lindeland is registered as general manager of LINDELAND MASKIN AS.

Where is LINDELAND MASKIN AS based?

LINDELAND MASKIN AS has its business address in Tonstad.

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.