BIZTRAC BETA
Non-specialised wholesale of food, beverages and tobacco

KING KONG COMPANY AS

Org. no. 918561838 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK −77,000
Equity NOK 2.6m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−77k kr).

KING KONG COMPANY AS is registered as a limited company in Oslo, Oslo with organisation number 918561838. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av dagligvarer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK −77,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK −77,000
Equity
NOK 2.6m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
1.81
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.1%
Very good
Equity as a share of total capital

Who owns KING KONG COMPANY AS?

JAWAD KAZEM MAHDI
KING KONG COMPANY AS
NOK 8.2m rev. · NOK −77,000 profit

KING KONG COMPANY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KING KONG COMPANY AS

Who owns KING KONG COMPANY AS?

JAWAD KAZEM MAHDI is the largest registered owner, with 100.0%.

What is the revenue of KING KONG COMPANY AS?

KING KONG COMPANY AS had revenue of NOK 8.2m in 2024.

Who is the general manager of KING KONG COMPANY AS?

Jawad Kazem Mahdi is registered as general manager of KING KONG COMPANY AS.

Where is KING KONG COMPANY AS based?

KING KONG COMPANY 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 15.06.2026.

Report a problem

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