BIZTRAC BETA
Retail sale of information and communication equipment

MEDIBRIX HOLDING AS

Org. no. 930836699 Limited company (AS) Harstad Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −148,000
Equity NOK 47.5m
Incorporated 2023
Share capital NOK 2.8m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−148k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MEDIBRIX HOLDING AS is registered as a limited company in Harstad, Troms with organisation number 930836699. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2023. Registered share capital is NOK 2.8m, divided into 933291 shares. The company's stated purpose is: “Investeringsselskap, herunder å investere i aksjer, obligasjoner, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −148,000
Equity
NOK 47.5m
Est. value
NOK 59.4m

Financial health · 2024

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

Who owns MEDIBRIX HOLDING AS?

BØRTIND INVEST AS
MEDIBRIX HOLDING AS
· NOK −148,000 profit

MEDIBRIX HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MEDIBRIX HOLDING AS own?

MEDIBRIX HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MEDIBRIX HOLDING AS er morselskap for 13 datterselskaper:

Frequently asked questions about MEDIBRIX HOLDING AS

Who owns MEDIBRIX HOLDING AS?

BØRTIND INVEST AS is the largest registered owner, with 93.3%.

Where is MEDIBRIX HOLDING AS based?

MEDIBRIX HOLDING AS has its business address in Harstad.

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.