BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

LTS MASKIN AS

Org. no. 983436978 Limited company (AS) Osterøy Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 49.6m
Operating profit NOK 2.5m
Equity NOK 4.1m
Incorporated 2001
Employees 16
Share capital NOK 101,000

LTS MASKIN AS is registered as a limited company in Osterøy, Vestland with organisation number 983436978. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2001 and has 16 registered employees. Registered share capital is NOK 101,000, divided into 1010 shares. The company's stated purpose is: “Kjøp og salg av maskiner og det som står i forbindelse med dette, samt varehandel. Videre skal selskapet utføre tjenester knyttet til bygg og anlegg, samt investere i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 49.6m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 49.6m
Operating profit
NOK 2.5m
Equity
NOK 4.1m
Est. value
NOK 10.6m

Financial health · 2024

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.8%
Satisfactory
Equity as a share of total capital

Who owns LTS MASKIN AS?

LEIF TORE SOLBERG
LTS MASKIN AS
NOK 49.6m rev. · NOK 2.5m profit

LTS MASKIN AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about LTS MASKIN AS

Who owns LTS MASKIN AS?

LEIF TORE SOLBERG is the largest registered owner, with 47.0%.

What is the revenue of LTS MASKIN AS?

LTS MASKIN AS had revenue of NOK 49.6m in 2024.

Who is the general manager of LTS MASKIN AS?

Ruben Solberg is registered as general manager of LTS MASKIN AS.

Where is LTS MASKIN AS based?

LTS MASKIN AS has its business address in Lonevåg.

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.