BIZTRAC BETA
General medical practice activities

MEDISINSK BEHANDLING AS

Org. no. 919298375 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 1.1m
Equity NOK 1.3m
Incorporated 2017
Employees 5
Share capital NOK 30,000

MEDISINSK BEHANDLING AS is registered as a limited company in Oslo, Oslo with organisation number 919298375. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2017 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive medisinsk behandling, investering, fotografering primært relatert til medisin, undervisning og alt annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 1.1m
Equity
NOK 1.3m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns MEDISINSK BEHANDLING AS?

LYVJABERG AS
MEDISINSK BEHANDLING AS
NOK 3.8m rev. · NOK 1.1m profit

MEDISINSK BEHANDLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEDISINSK BEHANDLING AS

Who owns MEDISINSK BEHANDLING AS?

LYVJABERG AS is the largest registered owner, with 100.0%.

What is the revenue of MEDISINSK BEHANDLING AS?

MEDISINSK BEHANDLING AS had revenue of NOK 3.8m in 2024.

Who is the general manager of MEDISINSK BEHANDLING AS?

Bård Magne Nordheim Kvam is registered as general manager of MEDISINSK BEHANDLING AS.

Where is MEDISINSK BEHANDLING AS based?

MEDISINSK BEHANDLING 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.