BIZTRAC BETA
Event catering activities

LØKKACATERING AS

Org. no. 822750192 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −11,000
Equity NOK −69,000
Incorporated 2019
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−69k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

LØKKACATERING AS is registered as a limited company in Ullensaker, Akershus with organisation number 822750192. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Catering - produksjon og salg av mat, drikke og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK −11,000
Equity
NOK −69,000

Financial health · 2025

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

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

Who owns LØKKACATERING AS?

CHAN KWONG CHU
LØKKACATERING AS
NOK 3.2m rev. · NOK −11,000 profit

LØKKACATERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØKKACATERING AS

Who owns LØKKACATERING AS?

CHAN KWONG CHU is the largest registered owner, with 50.0%.

What is the revenue of LØKKACATERING AS?

LØKKACATERING AS had revenue of NOK 3.2m in 2025.

Who is the general manager of LØKKACATERING AS?

Chan Kwong Chu is registered as general manager of LØKKACATERING AS.

Where is LØKKACATERING AS based?

LØKKACATERING AS has its business address in Jessheim.

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.