BIZTRAC BETA
Intermediation service activities for specialised retail sale

HAGEMO JAKT OG FRILUFT AS

Org. no. 928127699 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 30.3m
Operating profit NOK 469,000
Equity NOK 688,000
Incorporated 2021
Employees 5
Share capital NOK 30,000

HAGEMO JAKT OG FRILUFT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928127699. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av varer til jakt og fritidsbruk, kjøpe og selge jakt, jaktturer, samt guide jakt og alt som naturlig tilhører dette, og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.3m in revenue and NOK 469,000 in operating profit.

Key figures · 2024

Revenue
NOK 30.3m
Operating profit
NOK 469,000
Equity
NOK 688,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.0%
Weak
Equity as a share of total capital

Who owns HAGEMO JAKT OG FRILUFT AS?

HAGEMO GRUPPEN HOLDING AS
HAGEMO JAKT OG FRILUFT AS
NOK 30.3m rev. · NOK 469,000 profit

HAGEMO JAKT OG FRILUFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGEMO JAKT OG FRILUFT AS

Who owns HAGEMO JAKT OG FRILUFT AS?

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

What is the revenue of HAGEMO JAKT OG FRILUFT AS?

HAGEMO JAKT OG FRILUFT AS had revenue of NOK 30.3m in 2024.

Where is HAGEMO JAKT OG FRILUFT AS based?

HAGEMO JAKT OG FRILUFT AS has its business address in Leinstrand.

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.