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

NORGROSS AS

Org. no. 935556589 Limited company (AS) Enebakk Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK −2,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−2k kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-05-07 Adresseendring registrert 2026-05-07.

NORGROSS AS is registered as a limited company in Enebakk, Akershus with organisation number 935556589. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Engroshandel med alle typer matvarer til butikker, restauranter og andre serveringssteder. I tillegg salg av emballasje og andre pakke produkter.”.

Key figures

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 21,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns NORGROSS AS?

MUSTAFA KESER
NORGROSS AS
NOK 0 rev. · NOK −2,000 profit

NORGROSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORGROSS AS

Who owns NORGROSS AS?

MUSTAFA KESER is the largest registered owner, with 100.0%.

What is the revenue of NORGROSS AS?

NORGROSS AS had revenue of NOK 0.

Who is the general manager of NORGROSS AS?

Mustafa Keser is registered as general manager of NORGROSS AS.

Where is NORGROSS AS based?

NORGROSS AS has its business address in Ytre Enebakk.

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.