BIZTRAC BETA
Activities of fitness centres

SNERTINGDAL TRIMSENTER AS

Org. no. 997655060 Limited company (AS) Gjøvik Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 580,000
Operating profit NOK 451
Equity NOK 97,000
Incorporated 2011
Share capital NOK 100,000

SNERTINGDAL TRIMSENTER AS is registered as a limited company in Gjøvik, Innlandet with organisation number 997655060. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 2 shares. The company's stated purpose is: “Treningssenter og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 580,000 in revenue and NOK 451 in operating profit.

Key figures · 2024

Revenue
NOK 580,000
Operating profit
NOK 451
Equity
NOK 97,000
Est. value
NOK 41,000

Financial health · 2024

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

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

Who owns SNERTINGDAL TRIMSENTER AS?

MAI TOVE SVEUM
SNERTINGDAL TRIMSENTER AS
NOK 580,000 rev. · NOK 451 profit

SNERTINGDAL TRIMSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNERTINGDAL TRIMSENTER AS

Who owns SNERTINGDAL TRIMSENTER AS?

MAI TOVE SVEUM is the largest registered owner, with 100.0%.

What is the revenue of SNERTINGDAL TRIMSENTER AS?

SNERTINGDAL TRIMSENTER AS had revenue of NOK 580,000 in 2024.

Who is the general manager of SNERTINGDAL TRIMSENTER AS?

Mai Tove Sveum is registered as general manager of SNERTINGDAL TRIMSENTER AS.

Where is SNERTINGDAL TRIMSENTER AS based?

SNERTINGDAL TRIMSENTER AS has its business address in Snertingdal.

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.