BIZTRAC BETA
Sports and recreation education

GO'ONDT MASSASJE AS

Org. no. 928807924 Limited company (AS) Fauske Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 245,000
Operating profit NOK −6,000
Equity NOK 116,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

GO'ONDT MASSASJE AS is registered as a limited company in Fauske, Nordland with organisation number 928807924. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med massasje, trening i grupper og individuelt tilpasset. Samt andre tjenester knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 245,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 245,000
Operating profit
NOK −6,000
Equity
NOK 116,000
Est. value
NOK 274,000

Financial health · 2025

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

Who owns GO'ONDT MASSASJE AS?

BARBRO HELEN ELLINGSEN
GO'ONDT MASSASJE AS
NOK 245,000 rev. · NOK −6,000 profit

GO'ONDT MASSASJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GO'ONDT MASSASJE AS

Who owns GO'ONDT MASSASJE AS?

BARBRO HELEN ELLINGSEN is the largest registered owner, with 100.0%.

What is the revenue of GO'ONDT MASSASJE AS?

GO'ONDT MASSASJE AS had revenue of NOK 245,000 in 2025.

Who is the general manager of GO'ONDT MASSASJE AS?

Barbro Helen Ellingsen is registered as general manager of GO'ONDT MASSASJE AS.

Where is GO'ONDT MASSASJE AS based?

GO'ONDT MASSASJE AS has its business address in Valnesfjord.

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.