BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

LABMO AS

Org. no. 989276328 Limited company (AS) Bjørnafjorden Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 124,000
Operating profit NOK −454,000
Equity NOK 10.8m
Incorporated 2005
Share capital NOK 100,000

Signals

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

LABMO AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 989276328. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import og salg av laboratorieutstyr og måleinstrumenter, enhver virksomhet som står i forbindelse med dette, samt deltagelse i andre selskaper, investering i aksjer og andre verdipapirer, eiendom og dermed beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 124,000 in revenue and NOK −454,000 in operating profit.

Key figures · 2024

Revenue
NOK 124,000
Operating profit
NOK −454,000
Equity
NOK 10.8m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns LABMO AS?

TORE JØRN MOLDUNG
LABMO AS
NOK 124,000 rev. · NOK −454,000 profit

LABMO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LABMO AS

Who owns LABMO AS?

TORE JØRN MOLDUNG is the largest registered owner, with 50.0%.

What is the revenue of LABMO AS?

LABMO AS had revenue of NOK 124,000 in 2024.

Who is the general manager of LABMO AS?

Tore Jørn Moldung is registered as general manager of LABMO AS.

Where is LABMO AS based?

LABMO AS has its business address in Os.

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.