BIZTRAC BETA
COMPANY REGISTER PROFILE
917903484 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Wholesale of other food

GYMBUTIKKEN SENTRUM AS

Org. no. 917903484 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 454,000
Equity NOK 2.1m
Incorporated 2016
Share capital NOK 30,000

GYMBUTIKKEN SENTRUM AS is registered as a limited company in Oslo, Oslo with organisation number 917903484. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av helsekost, treningsutstyr, klær o.l. på nett og i butikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 454,000 in operating profit.

Former names: PERFORMANCE.R.US AS

Key figures · 2025

Revenue
NOK 3.3m
▼ −32 %
Operating profit
NOK 454,000
▼ −42 %
Equity
NOK 2.1m
▲ +20 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
4.72
Very good
Current assets ÷ current liabilities
Profitability
15.9%
Very good
Return on total assets
Solidity
78.8%
Very good
Equity as a share of total capital

Who owns GYMBUTIKKEN SENTRUM AS?

GYMBUTIKKEN SENTRUM AS
NOK 3.3m rev. · NOK 454,000 profit

GYMBUTIKKEN SENTRUM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYMBUTIKKEN SENTRUM AS

Who owns GYMBUTIKKEN SENTRUM AS?

XLNT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GYMBUTIKKEN SENTRUM AS?

GYMBUTIKKEN SENTRUM AS had revenue of NOK 3.3m in 2025.

Who is the general manager of GYMBUTIKKEN SENTRUM AS?

Mohammad Anwar is registered as general manager of GYMBUTIKKEN SENTRUM AS.

Where is GYMBUTIKKEN SENTRUM AS based?

GYMBUTIKKEN SENTRUM AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.