BIZTRAC BETA
Work training and permanently adapted work

AMESTRO AS

Org. no. 935587379 Limited company (AS) Lavangen Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 25.8m
Operating profit NOK 2.3m
Equity NOK 8.0m
Incorporated 1984
Employees 32
Share capital NOK 500,000

AMESTRO AS is registered as a limited company in Lavangen, Troms with organisation number 935587379. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1984 and has 32 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Drive praktisk opplæring, produksjon, handel og annet tjenesteytende arbeid ved bruk av arbeidskraft rekruttert blant fysisk og psykisk fungsjonshemmende og andre som ikke er i stand til å utføre arbeid på det ordinære arbeidsmarked. ”. The most recent filed accounts, for the 2024 financial year, show NOK 25.8m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 25.8m
Operating profit
NOK 2.3m
Equity
NOK 8.0m
Est. value
NOK 14.4m

Financial health · 2024

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

Who owns AMESTRO AS?

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

Which companies does AMESTRO AS own?

AMESTRO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AMESTRO AS

What is the revenue of AMESTRO AS?

AMESTRO AS had revenue of NOK 25.8m in 2024.

Who is the general manager of AMESTRO AS?

May Britt Flatmo is registered as general manager of AMESTRO AS.

Where is AMESTRO AS based?

AMESTRO AS has its business address in Tennevoll.

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.