BIZTRAC BETA
Performing arts activities in music

COCKTAIL SLIPPERS AS

Org. no. 912173062 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 387,000
Operating profit NOK 18,000
Equity NOK 33,000
Incorporated 2013
Share capital NOK 30,000

COCKTAIL SLIPPERS AS is registered as a limited company in Oslo, Oslo with organisation number 912173062. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 5000 shares. The company's stated purpose is: “Virksomhet innen musikk- og underholdningsbransjen, herunder plateinnspillinger, konserter og underholdning.”. The most recent filed accounts, for the 2025 financial year, show NOK 387,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 387,000
Operating profit
NOK 18,000
Equity
NOK 33,000
Est. value
NOK 96,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Weak
Equity as a share of total capital

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

Who owns COCKTAIL SLIPPERS AS?

KARIN SARA MARIA ANDERSSON
COCKTAIL SLIPPERS AS
NOK 387,000 rev. · NOK 18,000 profit

COCKTAIL SLIPPERS AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about COCKTAIL SLIPPERS AS

Who owns COCKTAIL SLIPPERS AS?

KARIN SARA MARIA ANDERSSON is the largest registered owner, with 20.0%.

What is the revenue of COCKTAIL SLIPPERS AS?

COCKTAIL SLIPPERS AS had revenue of NOK 387,000 in 2025.

Who is the general manager of COCKTAIL SLIPPERS AS?

Astrid Waller is registered as general manager of COCKTAIL SLIPPERS AS.

Where is COCKTAIL SLIPPERS AS based?

COCKTAIL SLIPPERS 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.