BIZTRAC BETA
Other health services

BERGEN BODY WORK AS

Org. no. 998414571 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 40,000
Equity NOK 86,000
Incorporated 2012
Share capital NOK 127,000

BERGEN BODY WORK AS is registered as a limited company in Bergen, Vestland with organisation number 998414571. The business is classified under other health services (NACE 86.993). The company was incorporated in 2012. Registered share capital is NOK 127,000, divided into 126600 shares. The company's stated purpose is: “Tjenester innen muskelterapi, idrettsmassasje, medisinsk massasje- og bindevevsbehandling, konsulenttjenester, kurs og kompetase innen fagområde helse, samt andre helsetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 40,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 40,000
Equity
NOK 86,000
Est. value
NOK 237,000

Financial health · 2025

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

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

Who owns BERGEN BODY WORK AS?

THERESE HANSEN
BERGEN BODY WORK AS
NOK 1.9m rev. · NOK 40,000 profit

BERGEN BODY WORK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN BODY WORK AS

Who owns BERGEN BODY WORK AS?

THERESE HANSEN is the largest registered owner, with 100.0%.

What is the revenue of BERGEN BODY WORK AS?

BERGEN BODY WORK AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BERGEN BODY WORK AS?

Therese Hansen is registered as general manager of BERGEN BODY WORK AS.

Where is BERGEN BODY WORK AS based?

BERGEN BODY WORK AS has its business address in Bergen.

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.