BIZTRAC BETA
General medical practice activities

MEDPOINT AS

Org. no. 828486462 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 691,000
Equity NOK 1.2m
Incorporated 2021
Share capital NOK 99,000

MEDPOINT AS is registered as a limited company in Oslo, Oslo with organisation number 828486462. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2021. Registered share capital is NOK 99,000, divided into 30000 shares. The company's stated purpose is: “Drift av legekontor og fastlegepraksis i tillegg til andre helsetjenester. Utleie av arbeidskraft og alt deromkring liggende. Eie og forvalte aksjer, andeler og andre former for deltakelse i andre virksomheter, annen konsulentvirksomhet i egen virksomhet og i andre selskap. Kjøp, salg og investering/utleie av eiendom, samt andre investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 691,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 691,000
Equity
NOK 1.2m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns MEDPOINT AS?

DANZIG AS
MEDPOINT AS
NOK 3.8m rev. · NOK 691,000 profit

MEDPOINT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MEDPOINT AS

Who owns MEDPOINT AS?

DANZIG AS is the largest registered owner, with 33.3%.

What is the revenue of MEDPOINT AS?

MEDPOINT AS had revenue of NOK 3.8m in 2024.

Who is the general manager of MEDPOINT AS?

Henrik Lind is registered as general manager of MEDPOINT AS.

Where is MEDPOINT AS based?

MEDPOINT AS has its business address in Oslo.

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.