BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

LIMACO AS

Org. no. 986977546 Limited company (AS) Holmestrand Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 24.3m
Operating profit NOK −1.6m
Equity NOK 9.5m
Incorporated 2004
Employees 11
Share capital NOK 1.4m

Signals

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

LIMACO AS is registered as a limited company in Holmestrand, Vestfold with organisation number 986977546. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2004 and has 11 registered employees. Registered share capital is NOK 1.4m, divided into 13500 shares. The company's stated purpose is: “Handel med varer og tjenester, utleie av driftsmidler og alt som dermed står i forbindelse, samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.3m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 24.3m
Operating profit
NOK −1.6m
Equity
NOK 9.5m
Est. value
NOK 20.2m

Financial health · 2024

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

Who owns LIMACO AS?

ID HOLDING AS
LIMACO AS
NOK 24.3m rev. · NOK −1.6m profit

LIMACO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIMACO AS

Who owns LIMACO AS?

ID HOLDING AS is the largest registered owner, with 90.2%.

What is the revenue of LIMACO AS?

LIMACO AS had revenue of NOK 24.3m in 2024.

Who is the general manager of LIMACO AS?

Inge Dalseth is registered as general manager of LIMACO AS.

Where is LIMACO AS based?

LIMACO AS has its business address in Holmestrand.

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.