BIZTRAC BETA
Day spa, sauna and steam bath activities

SPARKLING AS

Org. no. 914589436 Limited company (AS) Asker Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −184,000
Equity NOK 300,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−184k kr).

SPARKLING AS is registered as a limited company in Asker, Akershus with organisation number 914589436. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Hud og kroppsbehandling og salg av varer og annet som hører naturlig til dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −184,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −184,000
Equity
NOK 300,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns SPARKLING AS?

SARA BJÖRN
SPARKLING AS
NOK 1.6m rev. · NOK −184,000 profit

SPARKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPARKLING AS

Who owns SPARKLING AS?

SARA BJÖRN is the largest registered owner, with 100.0%.

What is the revenue of SPARKLING AS?

SPARKLING AS had revenue of NOK 1.6m in 2024.

Who is the general manager of SPARKLING AS?

Sara Björn is registered as general manager of SPARKLING AS.

Where is SPARKLING AS based?

SPARKLING AS has its business address in Heggedal.

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.