BIZTRAC BETA
Retail sale of sports equipment

LOFOTSPORT AS

Org. no. 897754592 Limited company (AS) Vestvågøy Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 19.5m
Operating profit NOK 2.2m
Equity NOK 10.4m
Incorporated 2011
Employees 13
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LOFOTSPORT AS is registered as a limited company in Vestvågøy, Nordland with organisation number 897754592. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2011 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel med sportsartikler og -utstyr og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.5m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 19.5m
Operating profit
NOK 2.2m
Equity
NOK 10.4m
Est. value
NOK 13.4m

Financial health · 2024

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

Who owns LOFOTSPORT AS?

LOFOTSPORT HOLDING AS
LOFOTSPORT AS
NOK 19.5m rev. · NOK 2.2m profit

LOFOTSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOFOTSPORT AS

Who owns LOFOTSPORT AS?

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

What is the revenue of LOFOTSPORT AS?

LOFOTSPORT AS had revenue of NOK 19.5m in 2024.

Who is the general manager of LOFOTSPORT AS?

Ketil Benjaminsen is registered as general manager of LOFOTSPORT AS.

Where is LOFOTSPORT AS based?

LOFOTSPORT AS has its business address in Leknes.

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.