biztrac. BETA
COMPANY REGISTER PROFILE
921505337 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

PUNJAB LØKKA AS

Org. no. 921505337 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 11.1m
Operating profit NOK 704,000
Equity NOK −986,000
Incorporated 2018
Employees 34
Share capital NOK 100,000

Signals

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

PUNJAB LØKKA AS is registered as a limited company in Oslo, Oslo with organisation number 921505337. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 34 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive restaurantvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.1m in revenue and NOK 704,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.1m
▲ +3 %
Operating profit
NOK 704,000
▲ +137 %
Equity
NOK −986,000
▲ +42 %

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
12.5%
Good
Return on total assets
Solidity
-18.0%
Weak
Equity as a share of total capital

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

Who owns PUNJAB LØKKA AS?

PUNJAB LØKKA AS
NOK 11.1m rev. · NOK 704,000 profit

PUNJAB LØKKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PUNJAB LØKKA AS

Who owns PUNJAB LØKKA AS?

PUNJAB EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of PUNJAB LØKKA AS?

PUNJAB LØKKA AS had revenue of NOK 11.1m in 2025.

Who is the general manager of PUNJAB LØKKA AS?

Gurkirt Singh is registered as general manager of PUNJAB LØKKA AS.

Where is PUNJAB LØKKA AS based?

PUNJAB LØKKA AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.