BIZTRAC BETA
Other health services

SKIN STORIES AS

Org. no. 927870444 Limited company (AS) Ringerike Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 29,000
Equity NOK −193,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−193k kr).

SKIN STORIES AS is registered as a limited company in Ringerike, Buskerud with organisation number 927870444. The business is classified under other health services (NACE 86.993). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Medisinsk estetisk hudklinikk. Hudbehandlinger og salg av produkter. Salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 29,000
Equity
NOK −193,000
Est. value
NOK 160,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-95.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SKIN STORIES AS?

MORTEN ALEXANDER MALCOLM AYLING
SKIN STORIES AS
NOK 2.0m rev. · NOK 29,000 profit

SKIN STORIES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKIN STORIES AS

Who owns SKIN STORIES AS?

MORTEN ALEXANDER MALCOLM AYLING is the largest registered owner, with 50.0%.

What is the revenue of SKIN STORIES AS?

SKIN STORIES AS had revenue of NOK 2.0m in 2025.

Who is the general manager of SKIN STORIES AS?

Mari Brodahl Øvrelid is registered as general manager of SKIN STORIES AS.

Where is SKIN STORIES AS based?

SKIN STORIES AS has its business address in Hønefoss.

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.