BIZTRAC BETA
Repair and maintenance of motor vehicles

SØRUM BIL & LAKK AS

Org. no. 917095159 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 1.2m
Equity NOK 837,000
Incorporated 2016
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

SØRUM BIL & LAKK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 917095159. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å utføre vedlikehold, reparasjon, oppretting og lakkering av motorvogner.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 1.2m
Equity
NOK 837,000
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns SØRUM BIL & LAKK AS?

YASSER ELDIRAWI
SØRUM BIL & LAKK AS
NOK 4.8m rev. · NOK 1.2m profit

SØRUM BIL & LAKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRUM BIL & LAKK AS

Who owns SØRUM BIL & LAKK AS?

YASSER ELDIRAWI is the largest registered owner, with 100.0%.

What is the revenue of SØRUM BIL & LAKK AS?

SØRUM BIL & LAKK AS had revenue of NOK 4.8m in 2024.

Who is the general manager of SØRUM BIL & LAKK AS?

Yasser Eldirawi is registered as general manager of SØRUM BIL & LAKK AS.

Where is SØRUM BIL & LAKK AS based?

SØRUM BIL & LAKK AS has its business address in Sørumsand.

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.