BIZTRAC BETA
Activities of agents involved in non-specialised wholesale

GB SPORT AS

Org. no. 920331246 Limited company (AS) Vaksdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −249,000
Equity NOK 374,000
Incorporated 2017
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−249k kr).

GB SPORT AS is registered as a limited company in Vaksdal, Vestland with organisation number 920331246. The business is classified under activities of agents involved in non-specialised wholesale (NACE 46.190). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 150 shares. The company's stated purpose is: “Import, distribusjon og salg av varer. Konsulenttjenester innen drift og prosjektledelse og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −249,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −249,000
Equity
NOK 374,000
Est. value
NOK 407,000

Financial health · 2024

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

Who owns GB SPORT AS?

KIM ANDRÉ HOP GREGERSEN
GB SPORT AS
NOK 1.5m rev. · NOK −249,000 profit

GB SPORT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GB SPORT AS

Who owns GB SPORT AS?

KIM ANDRÉ HOP GREGERSEN is the largest registered owner, with 33.3%.

What is the revenue of GB SPORT AS?

GB SPORT AS had revenue of NOK 1.5m in 2024.

Who is the general manager of GB SPORT AS?

Eirik Wefring Bjørkheim is registered as general manager of GB SPORT AS.

Where is GB SPORT AS based?

GB SPORT AS has its business address in Dalekvam.

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.