BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

LUMIBIRD MEDICAL NORDICS AS

Org. no. 979311494 Limited company (AS) Asker Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK −444,000
Equity NOK 2.2m
Incorporated 1997
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−444k kr).

LUMIBIRD MEDICAL NORDICS AS is registered as a limited company in Asker, Akershus with organisation number 979311494. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 2000 shares. The company's stated purpose is: “Markedsføre og selge produkter i Norge.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK −444,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK −444,000
Equity
NOK 2.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns LUMIBIRD MEDICAL NORDICS AS?

LUMIBIRD MEDICAL
LUMIBIRD MEDICAL NORDICS AS
NOK 8.4m rev. · NOK −444,000 profit

LUMIBIRD MEDICAL NORDICS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LUMIBIRD MEDICAL NORDICS AS er morselskap for 1 datterselskap:

Frequently asked questions about LUMIBIRD MEDICAL NORDICS AS

Who owns LUMIBIRD MEDICAL NORDICS AS?

LUMIBIRD MEDICAL is the largest registered owner, with 100.0%.

What is the revenue of LUMIBIRD MEDICAL NORDICS AS?

LUMIBIRD MEDICAL NORDICS AS had revenue of NOK 8.4m in 2024.

Where is LUMIBIRD MEDICAL NORDICS AS based?

LUMIBIRD MEDICAL NORDICS AS has its business address in Billingstad.

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.