biztrac. BETA
COMPANY REGISTER PROFILE
935828309 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

SMARTSPA AS

Org. no. 935828309 Limited company (AS) Bømlo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 556,000
Operating profit NOK 43,000
Equity NOK 57,000
Incorporated 2025
Share capital NOK 30,000

SMARTSPA AS is registered as a limited company in Bømlo, Vestland with organisation number 935828309. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg, import og utvikling av spa-produkter, samt investering i relaterte selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 556,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 556,000
Operating profit
NOK 43,000
Equity
NOK 57,000
Est. value
NOK 188,000

Financial health · 2025

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

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

Who owns SMARTSPA AS?

SMARTSPA AS
NOK 556,000 rev. · NOK 43,000 profit

SMARTSPA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMARTSPA AS

Who owns SMARTSPA AS?

TARANGER HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of SMARTSPA AS?

SMARTSPA AS had revenue of NOK 556,000 in 2025.

Who is the general manager of SMARTSPA AS?

Markus Stoknes Taranger is registered as general manager of SMARTSPA AS.

Where is SMARTSPA AS based?

SMARTSPA AS has its business address in Mosterhamn.

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.