BIZTRAC BETA
Retail sale of motor vehicles

SEBIL AS

Org. no. 932456362 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 100,000
Incorporated 2023
Share capital NOK 100,000

Signals

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

SEBIL AS is registered as a limited company in Drammen, Buskerud with organisation number 932456362. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av brukte biler, utleie av biler, billakkering og service, samt andre produkter/ tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 100,000
Est. value
NOK 125,000

Financial health · 2024

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

Who owns SEBIL AS?

BILNETT AS
SEBIL AS
NOK 0 rev. · NOK −10,000 profit

SEBIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEBIL AS

Who owns SEBIL AS?

BILNETT AS is the largest registered owner, with 100.0%.

What is the revenue of SEBIL AS?

SEBIL AS had revenue of NOK 0 in 2024.

Who is the general manager of SEBIL AS?

Aram Saleh Kakamala is registered as general manager of SEBIL AS.

Where is SEBIL AS based?

SEBIL AS has its business address in Drammen.

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.