BIZTRAC BETA
Retail sale of sports equipment

JEGERSERVICE AS

Org. no. 996944670 Limited company (AS) Nome Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK −152,000
Equity NOK 52,000
Incorporated 2011
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−152k kr).

JEGERSERVICE AS is registered as a limited company in Nome, Telemark with organisation number 996944670. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Handel med telekommunikasjonsutstyr, generell varehandel, konsulenttjenester innen telematikk-elektro, import, samt hva herved står i forbindelse. Selskapet kan også ved aksjetegning eller på annen måte delta i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK −152,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK −152,000
Equity
NOK 52,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JEGERSERVICE AS?

ØVJE INVEST AS
JEGERSERVICE AS
NOK 3.0m rev. · NOK −152,000 profit

JEGERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JEGERSERVICE AS

Who owns JEGERSERVICE AS?

ØVJE INVEST AS is the largest registered owner, with 51.0%.

What is the revenue of JEGERSERVICE AS?

JEGERSERVICE AS had revenue of NOK 3.0m in 2025.

Where is JEGERSERVICE AS based?

JEGERSERVICE AS has its business address in Ulefoss.

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.