BIZTRAC BETA
Restaurant activities

JAG RESTAURANTS AS

Org. no. 822126472 Limited company (AS) Tromsø Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −109,000
Equity NOK −10.1m
Incorporated 2019
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−10,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−109k kr).

JAG RESTAURANTS AS is registered as a limited company in Tromsø, Troms with organisation number 822126472. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eie og investere i aksjer samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −109,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −109,000
Equity
NOK −10.1m

Financial health · 2024

Liquidity
109.41
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1101.3%
Weak
Equity as a share of total capital

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

Who owns JAG RESTAURANTS AS?

AMJ CAPITAL AS
JAG RESTAURANTS AS
NOK 0 rev. · NOK −109,000 profit

JAG RESTAURANTS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does JAG RESTAURANTS AS own?

JAG RESTAURANTS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JAG RESTAURANTS AS

Who owns JAG RESTAURANTS AS?

AMJ CAPITAL AS is the largest registered owner, with 34.0%.

What is the revenue of JAG RESTAURANTS AS?

JAG RESTAURANTS AS had revenue of NOK 0 in 2024.

Where is JAG RESTAURANTS AS based?

JAG RESTAURANTS AS has its business address in Tromsø.

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.