BIZTRAC BETA
Retail sale of sports equipment

JAKT & FISKESPESIALISTEN AS

Org. no. 993366498 Limited company (AS) Molde Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 25.3m
Operating profit NOK 322,000
Equity NOK 4.9m
Incorporated 2008
Employees 7
Share capital NOK 30,000

JAKT & FISKESPESIALISTEN AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 993366498. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2008 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av utstyr innen jakt, fiske og friluftsliv, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.3m in revenue and NOK 322,000 in operating profit.

Key figures · 2024

Revenue
NOK 25.3m
Operating profit
NOK 322,000
Equity
NOK 4.9m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns JAKT & FISKESPESIALISTEN AS?

OLA THUE
JAKT & FISKESPESIALISTEN AS
NOK 25.3m rev. · NOK 322,000 profit

JAKT & FISKESPESIALISTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JAKT & FISKESPESIALISTEN AS

Who owns JAKT & FISKESPESIALISTEN AS?

OLA THUE is the largest registered owner, with 90.0%.

What is the revenue of JAKT & FISKESPESIALISTEN AS?

JAKT & FISKESPESIALISTEN AS had revenue of NOK 25.3m in 2024.

Who is the general manager of JAKT & FISKESPESIALISTEN AS?

Ola Thue is registered as general manager of JAKT & FISKESPESIALISTEN AS.

Where is JAKT & FISKESPESIALISTEN AS based?

JAKT & FISKESPESIALISTEN AS has its business address in Molde.

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.