BIZTRAC BETA
Day spa, sauna and steam bath activities

OOY THAIMASSASJE AS

Org. no. 923405526 Limited company (AS) Sandnes Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 647,000
Operating profit NOK −39,000
Equity NOK 84,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39k kr).

OOY THAIMASSASJE AS is registered as a limited company in Sandnes, Rogaland with organisation number 923405526. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Massasjeklinikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 647,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 647,000
Operating profit
NOK −39,000
Equity
NOK 84,000
Est. value
NOK 493,000

Financial health · 2024

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

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

Who owns OOY THAIMASSASJE AS?

PAIRIN LILJESTRAND
OOY THAIMASSASJE AS
NOK 647,000 rev. · NOK −39,000 profit

OOY THAIMASSASJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OOY THAIMASSASJE AS

Who owns OOY THAIMASSASJE AS?

PAIRIN LILJESTRAND is the largest registered owner, with 100.0%.

What is the revenue of OOY THAIMASSASJE AS?

OOY THAIMASSASJE AS had revenue of NOK 647,000 in 2025.

Who is the general manager of OOY THAIMASSASJE AS?

Pairin Liljestrand is registered as general manager of OOY THAIMASSASJE AS.

Where is OOY THAIMASSASJE AS based?

OOY THAIMASSASJE AS has its business address in Sandnes.

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.