BIZTRAC BETA
Hairdressing and barber activities

AUDS HUDPLEIE AQUARAMA AS

Org. no. 932361221 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 529,000
Equity NOK 476,000
Incorporated 2023
Share capital NOK 30,000

AUDS HUDPLEIE AQUARAMA AS is registered as a limited company in Kristiansand, Agder with organisation number 932361221. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive hudpleiesalong og handelsvirksomhet, samt hva herved står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 529,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 529,000
Equity
NOK 476,000
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns AUDS HUDPLEIE AQUARAMA AS?

AUDS HUDPLEIE MARKENS AS
AUDS HUDPLEIE AQUARAMA AS
NOK 3.5m rev. · NOK 529,000 profit

AUDS HUDPLEIE AQUARAMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUDS HUDPLEIE AQUARAMA AS

Who owns AUDS HUDPLEIE AQUARAMA AS?

AUDS HUDPLEIE MARKENS AS is the largest registered owner, with 100.0%.

What is the revenue of AUDS HUDPLEIE AQUARAMA AS?

AUDS HUDPLEIE AQUARAMA AS had revenue of NOK 3.5m in 2025.

Who is the general manager of AUDS HUDPLEIE AQUARAMA AS?

Monica Andersen is registered as general manager of AUDS HUDPLEIE AQUARAMA AS.

Where is AUDS HUDPLEIE AQUARAMA AS based?

AUDS HUDPLEIE AQUARAMA AS has its business address in Kristiansand S.

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.