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

KONG DAGLIGVARER AS

Org. no. 930865583 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −18,000
Equity NOK 128,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KONG DAGLIGVARER AS is registered as a limited company in Kongsberg, Buskerud with organisation number 930865583. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av dagligvarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −18,000
Equity
NOK 128,000
Est. value
NOK 731,000

Financial health · 2024

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

Who owns KONG DAGLIGVARER AS?

MOHAMMAD KAISS MAHMOUD
KONG DAGLIGVARER AS
NOK 2.1m rev. · NOK −18,000 profit

KONG DAGLIGVARER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONG DAGLIGVARER AS

Who owns KONG DAGLIGVARER AS?

MOHAMMAD KAISS MAHMOUD is the largest registered owner, with 100.0%.

What is the revenue of KONG DAGLIGVARER AS?

KONG DAGLIGVARER AS had revenue of NOK 2.1m in 2024.

Who is the general manager of KONG DAGLIGVARER AS?

Mohammad Kaiss Mahmoud is registered as general manager of KONG DAGLIGVARER AS.

Where is KONG DAGLIGVARER AS based?

KONG DAGLIGVARER AS has its business address in Kongsberg.

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.