BIZTRAC BETA
Buying and selling of own real estate

OSLO DERMATOLOGY AS

Org. no. 812603612 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 9.3m
Operating profit NOK 4.4m
Equity NOK 29.1m
Incorporated 2013
Share capital NOK 30,000

OSLO DERMATOLOGY AS is registered as a limited company in Oslo, Oslo with organisation number 812603612. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom til selskaper og privatpersoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.3m in revenue and NOK 4.4m in operating profit.

Key figures · 2024

Revenue
NOK 9.3m
Operating profit
NOK 4.4m
Equity
NOK 29.1m
Est. value
NOK 32.4m

Financial health · 2024

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

Who owns OSLO DERMATOLOGY AS?

MAYA TIGALONOVA-WALISZEWSKA
OSLO DERMATOLOGY AS
NOK 9.3m rev. · NOK 4.4m profit

OSLO DERMATOLOGY AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OSLO DERMATOLOGY AS own?

OSLO DERMATOLOGY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OSLO DERMATOLOGY AS

Who owns OSLO DERMATOLOGY AS?

MAYA TIGALONOVA-WALISZEWSKA is the largest registered owner, with 53.3%.

What is the revenue of OSLO DERMATOLOGY AS?

OSLO DERMATOLOGY AS had revenue of NOK 9.3m in 2024.

Who is the general manager of OSLO DERMATOLOGY AS?

Maya Tigalonova-Waliszewska is registered as general manager of OSLO DERMATOLOGY AS.

Where is OSLO DERMATOLOGY AS based?

OSLO DERMATOLOGY 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.