BIZTRAC BETA
Wholesale of information and communication equipment

AS LARVIK ENGRO

Org. no. 826501952 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 28,000
Equity NOK −259,000
Incorporated 2020
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−259k kr).

AS LARVIK ENGRO is registered as a limited company in Larvik, Vestfold with organisation number 826501952. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Netthandel og reparasjon av elektronikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 28,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 28,000
Equity
NOK −259,000
Est. value
NOK 207,000

Financial health · 2024

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

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

Who owns AS LARVIK ENGRO?

ALLADIN HINDAWI
AS LARVIK ENGRO
NOK 3.8m rev. · NOK 28,000 profit

AS LARVIK ENGRO has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS LARVIK ENGRO

Who owns AS LARVIK ENGRO?

ALLADIN HINDAWI is the largest registered owner, with 50.0%.

What is the revenue of AS LARVIK ENGRO?

AS LARVIK ENGRO had revenue of NOK 3.8m in 2024.

Who is the general manager of AS LARVIK ENGRO?

Alladin Hindawi is registered as general manager of AS LARVIK ENGRO.

Where is AS LARVIK ENGRO based?

AS LARVIK ENGRO has its business address in Larvik.

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.