BIZTRAC BETA
Wholesale of information and communication equipment

ELBILGROSSISTEN AS

Org. no. 924631368 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 23.1m
Operating profit NOK −2.2m
Equity NOK 1.6m
Incorporated 2020
Employees 14
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

ELBILGROSSISTEN AS is registered as a limited company in Oslo, Oslo with organisation number 924631368. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2020 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og import av elektriske produkter, tilbehør og tjenester til forbruker.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.1m in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 23.1m
Operating profit
NOK −2.2m
Equity
NOK 1.6m
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns ELBILGROSSISTEN AS?

EBG HOLDING AS
ELBILGROSSISTEN AS
NOK 23.1m rev. · NOK −2.2m profit

ELBILGROSSISTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELBILGROSSISTEN AS

Who owns ELBILGROSSISTEN AS?

EBG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ELBILGROSSISTEN AS?

ELBILGROSSISTEN AS had revenue of NOK 23.1m in 2024.

Who is the general manager of ELBILGROSSISTEN AS?

Sang Huynh is registered as general manager of ELBILGROSSISTEN AS.

Where is ELBILGROSSISTEN AS based?

ELBILGROSSISTEN 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.