BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

JEDI AS

Org. no. 927181320 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 543,000
Equity NOK −171,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−171k kr).

JEDI AS is registered as a limited company in Bergen, Vestland with organisation number 927181320. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive handel med dagligvarer og alt som står i forbindelse med dette i tillegg skal selskapet driver med catering, logistikk og transport av varer, renhold og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 543,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 543,000
Equity
NOK −171,000
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.5%
Weak
Equity as a share of total capital

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

Who owns JEDI AS?

HARJINDER SINGH PANESAR
JEDI AS
NOK 2.1m rev. · NOK 543,000 profit

JEDI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JEDI AS

Who owns JEDI AS?

HARJINDER SINGH PANESAR is the largest registered owner, with 50.0%.

What is the revenue of JEDI AS?

JEDI AS had revenue of NOK 2.1m in 2025.

Where is JEDI AS based?

JEDI AS has its business address in Fyllingsdalen.

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.