BIZTRAC BETA
Activities of fitness centres

RAUMA TRENINGSSENTER AS

Org. no. 994881930 Limited company (AS) Rauma Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 4,000
Equity NOK 918,000
Incorporated 2009
Employees 11
Share capital NOK 30,000

RAUMA TRENINGSSENTER AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 994881930. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2009 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av treningssenter og alt som står i forbindelse med dette, herunder deltakelse i andre selskaper i tilsvarende bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 4,000
Equity
NOK 918,000
Est. value
NOK 396,000

Financial health · 2025

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

Who owns RAUMA TRENINGSSENTER AS?

BENDIK SØRLI
RAUMA TRENINGSSENTER AS
NOK 2.5m rev. · NOK 4,000 profit

RAUMA TRENINGSSENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAUMA TRENINGSSENTER AS

Who owns RAUMA TRENINGSSENTER AS?

BENDIK SØRLI is the largest registered owner, with 50.0%.

What is the revenue of RAUMA TRENINGSSENTER AS?

RAUMA TRENINGSSENTER AS had revenue of NOK 2.5m in 2025.

Who is the general manager of RAUMA TRENINGSSENTER AS?

Bendik Sørli is registered as general manager of RAUMA TRENINGSSENTER AS.

Where is RAUMA TRENINGSSENTER AS based?

RAUMA TRENINGSSENTER AS has its business address in Åndalsnes.

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.