biztrac. BETA
COMPANY REGISTER PROFILE
980895637 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other health services

OSLO HODEPINESENTER AS

Org. no. 980895637 Limited company (AS) Oslo Incorporated 1998 Active
Revenue 2025 NOK 4.2m
Operating profit NOK 1.3m
Equity NOK 1.8m
Incorporated 1998
Employees 5
Share capital NOK 100,000

OSLO HODEPINESENTER AS is registered as a limited company in Oslo, Oslo with organisation number 980895637. The business is classified under other health services (NACE 86.993). The company was incorporated in 1998 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Medisinsk virksomhet, og tilliggende virksomhet, herunder deltagelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 1.3m in operating profit.

Former names: SJØLYST MEDISINSKE LASERKLINIKK AS, ANNE CHRISTINE POOLE AS, OSLO MIGRENEKLINIKK AS

Key figures · 2025

Revenue
NOK 4.2m
▲ +53 %
Operating profit
NOK 1.3m
▲ +333 %
Equity
NOK 1.8m
▲ +111 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
2.84
Very good
Current assets ÷ current liabilities
Profitability
64.6%
Very good
Return on total assets
Solidity
72.1%
Very good
Equity as a share of total capital

Who owns OSLO HODEPINESENTER AS?

OSLO HODEPINESENTER AS
NOK 4.2m rev. · NOK 1.3m profit

OSLO HODEPINESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO HODEPINESENTER AS

Who owns OSLO HODEPINESENTER AS?

Anne Christine Poole is the largest registered owner, with 100.0%.

What is the revenue of OSLO HODEPINESENTER AS?

OSLO HODEPINESENTER AS had revenue of NOK 4.2m in 2025.

Where is OSLO HODEPINESENTER AS based?

OSLO HODEPINESENTER 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.