BIZTRAC BETA
Work training and permanently adapted work

ASTERO MEKANISK AS

Org. no. 932860554 Limited company (AS) Molde Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 46.7m
Operating profit NOK 4.1m
Equity NOK 10.2m
Incorporated 2024
Employees 33
Share capital NOK 200,000

ASTERO MEKANISK AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 932860554. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 2024 and has 33 registered employees. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er leverandør av mekanisk skreddersøm som verktøy og pedagogisk virkemiddel i gjennomføring av kurs, praksis og kvalifisering for arbeidssøkere.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.7m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 46.7m
Operating profit
NOK 4.1m
Equity
NOK 10.2m
Est. value
NOK 21.4m

Financial health · 2024

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

Who owns ASTERO MEKANISK AS?

ASTERO AS
ASTERO MEKANISK AS
NOK 46.7m rev. · NOK 4.1m profit

ASTERO MEKANISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASTERO MEKANISK AS

Who owns ASTERO MEKANISK AS?

ASTERO AS is the largest registered owner, with 100.0%.

What is the revenue of ASTERO MEKANISK AS?

ASTERO MEKANISK AS had revenue of NOK 46.7m in 2024.

Who is the general manager of ASTERO MEKANISK AS?

Bjørnar Nerlandsrem Vetvik is registered as general manager of ASTERO MEKANISK AS.

Where is ASTERO MEKANISK AS based?

ASTERO MEKANISK AS has its business address in Molde.

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.