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

A-ONE BEAUTY AS

Org. no. 933702480 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

A-ONE BEAUTY AS is registered as a limited company in Oslo, Oslo with organisation number 933702480. The business is classified under other health services (NACE 86.993). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Medisinsk klinikk, serveringssted og butikkvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: SHM240601 AS

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 46,000

Financial health · 2024

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

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

Who owns A-ONE BEAUTY AS?

OLGA DMITRIEVNA KOLOTOVKINA BORBA PT
A-ONE BEAUTY AS
NOK 0 rev. · NOK 0 profit

A-ONE BEAUTY AS has 1 registered shareholder:

  • OLGA DMITRIEVNA KOLOTOVKINA BORBA 100.0%

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about A-ONE BEAUTY AS

Who owns A-ONE BEAUTY AS?

OLGA DMITRIEVNA KOLOTOVKINA BORBA is the largest registered owner, with 100.0%.

What is the revenue of A-ONE BEAUTY AS?

A-ONE BEAUTY AS had revenue of NOK 0 in 2024.

Where is A-ONE BEAUTY AS based?

A-ONE BEAUTY 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.