BIZTRAC BETA
COMPANY REGISTER PROFILE
937147376 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

STRYN SPORT AS

Org. no. 937147376 Limited company (AS) Stryn Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Employees 8
Share capital NOK 300,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-08.

STRYN SPORT AS is registered as a limited company in Stryn, Vestland with organisation number 937147376. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2026 and has 8 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drive butikkhandel med sportsutstyr, herunder, men ikke begrenset til, salg av utstyr og klær til ulike sportsgrener, treningsutstyr, tilbehør og sikkerhetsutstyr, samt rådgivning og kundestøtte relatert til sports- og treningsprodukter.”.

Who owns STRYN SPORT AS?

No shareholders are registered for STRYN SPORT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STRYN SPORT AS

Who is the general manager of STRYN SPORT AS?

Kai Magne Kjersem is registered as general manager of STRYN SPORT AS.

Where is STRYN SPORT AS based?

STRYN SPORT AS has its business address in Stryn.

Property

Business address Tonningsgata 16, 6783 Stryn
Cadastral unit 4651-57/15/0/0
Building Store sammenbygde boligbygg på 3 og 4 etg · 13 units

10 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.