BIZTRAC BETA
Research and experimental development on natural sciences and engineering

ASAMEDIC AS

Org. no. 912575586 Limited company (AS) Nordre Follo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −11.0m
Equity NOK 32.1m
Incorporated 2013
Share capital NOK 93,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11,0 mill kr).
  • Nylig endring 2026-04-24 Aksjekapital registrert 2026-04-24.

ASAMEDIC AS is registered as a limited company in Nordre Follo, Akershus with organisation number 912575586. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2013. Registered share capital is NOK 93,000, divided into 3112258 shares. The company's stated purpose is: “Utvikle og markedsføre legemidler og alt som er i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −11.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −11.0m
Equity
NOK 32.1m
Est. value
NOK 17.0m

Financial health · 2024

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

Who owns ASAMEDIC AS?

HAMEC AS
ASAMEDIC AS
NOK 1.2m rev. · NOK −11.0m profit

ASAMEDIC AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about ASAMEDIC AS

Who owns ASAMEDIC AS?

HAMEC AS is the largest registered owner, with 25.2%.

What is the revenue of ASAMEDIC AS?

ASAMEDIC AS had revenue of NOK 1.2m in 2024.

Who is the general manager of ASAMEDIC AS?

Geir Ivar Westen is registered as general manager of ASAMEDIC AS.

Where is ASAMEDIC AS based?

ASAMEDIC AS has its business address in Trollåsen.

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.