BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

LIFT 24 AS

Org. no. 929139410 Limited company (AS) Nesna Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −34,000
Equity NOK −31,000
Incorporated 2022
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−31k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−34k kr).

LIFT 24 AS is registered as a limited company in Nesna, Nordland with organisation number 929139410. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 30 shares. The company's stated purpose is: “Salg av anleggsmaskiner og materialer, utleie av anleggsmaskiner.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK −31,000

Financial health · 2024

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

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

Who owns LIFT 24 AS?

Marcin Andrzej Loski
LIFT 24 AS
NOK 0 rev. · NOK −34,000 profit

LIFT 24 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIFT 24 AS

Who owns LIFT 24 AS?

Marcin Andrzej Loski is the largest registered owner, with 36.7%.

What is the revenue of LIFT 24 AS?

LIFT 24 AS had revenue of NOK 0 in 2024.

Who is the general manager of LIFT 24 AS?

Jacek Adam Pyrzak is registered as general manager of LIFT 24 AS.

Where is LIFT 24 AS based?

LIFT 24 AS has its business address in Nesna.

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.