BIZTRAC BETA
General medical practice activities

PULSMED AS

Org. no. 923350977 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 135,000
Equity NOK 4.6m
Incorporated 2019
Share capital NOK 30,000

PULSMED AS is registered as a limited company in Oslo, Oslo with organisation number 923350977. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Helse tjeneste, privatlege tjeneste. Kjøp og utleie av eiendom og kjøp og utleie av båt, samt virksomhet som står i naturlig forbindelse med dette, herunder deltakelse i andre virksomheter samt lege virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 135,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 135,000
Equity
NOK 4.6m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns PULSMED AS?

HOSSEIN KHORSHIDI
PULSMED AS
NOK 2.9m rev. · NOK 135,000 profit

PULSMED AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PULSMED AS own?

PULSMED AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PULSMED AS

Who owns PULSMED AS?

HOSSEIN KHORSHIDI is the largest registered owner, with 50.0%.

What is the revenue of PULSMED AS?

PULSMED AS had revenue of NOK 2.9m in 2024.

Who is the general manager of PULSMED AS?

Hossein Khorshidi is registered as general manager of PULSMED AS.

Where is PULSMED AS based?

PULSMED 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.