biztrac. BETA
COMPANY REGISTER PROFILE
933663981 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sports activities n.e.c.

STYRKESENTERET AS

Org. no. 933663981 Limited company (AS) Giske Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 16,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

STYRKESENTERET AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 933663981. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive på med aktiviteter som fremmer fysisk og psykisk fostring, samt tjenester og produkter relatert til dette.”.

Key figures · 2025

Operating profit
NOK −7,000
▼ −1031 %
Equity
NOK 16,000
▼ −30 %
Est. value
NOK 21,000

Financial health · 2025

Liquidity
-32.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.0%
Not satisfactory
Return on total assets
Solidity
5.2%
Weak
Equity as a share of total capital

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

Who owns STYRKESENTERET AS?

STYRKESENTERET AS
· NOK −7,000 profit

STYRKESENTERET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STYRKESENTERET AS own?

STYRKESENTERET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STYRKESENTERET AS

Who owns STYRKESENTERET AS?

Gro Helen Kaldhussæter is the largest registered owner, with 100.0%.

Who is the general manager of STYRKESENTERET AS?

Gro Helen Kaldhussæter is registered as general manager of STYRKESENTERET AS.

Where is STYRKESENTERET AS based?

STYRKESENTERET AS has its business address in Valderøya.

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

Report a problem

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