BIZTRAC BETA
Work training and permanently adapted work

AMENTO AS

Org. no. 927643863 Limited company (AS) Lyngdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 17.5m
Operating profit NOK −1.2m
Equity NOK 33.1m
Incorporated 2021
Employees 21
Share capital NOK 110,000

Signals

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

AMENTO AS is registered as a limited company in Lyngdal, Agder with organisation number 927643863. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 2021 and has 21 registered employees. Registered share capital is NOK 110,000, divided into 100000 shares. The company's stated purpose is: “Å drive arbeids- og inkluderingsaktiviteter gjennom avklaring, arbeidstrening og kvalifisering, med sikte på formidling til ordinært arbeid. Egne produksjonsavdelinger vil være viktige arenaer i et slikt arbeid. Selskapet har ikke økonomisk erverv til formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.5m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 17.5m
Operating profit
NOK −1.2m
Equity
NOK 33.1m
Est. value
NOK 28.4m

Financial health · 2024

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

Who owns AMENTO AS?

No shareholders are registered for AMENTO AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about AMENTO AS

What is the revenue of AMENTO AS?

AMENTO AS had revenue of NOK 17.5m in 2024.

Who is the general manager of AMENTO AS?

Tove Løkke-Øwre is registered as general manager of AMENTO AS.

Where is AMENTO AS based?

AMENTO 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.