BIZTRAC BETA
Retail sale of motor vehicles

DRØMMEBIL AS

Org. no. 932177080 Limited company (AS) Ullensaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 132,000
Equity NOK 57,000
Incorporated 2023
Share capital NOK 30,000

DRØMMEBIL AS is registered as a limited company in Ullensaker, Akershus with organisation number 932177080. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Kjøp, salg samt import og eksport av brukte biler og bildeler og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet. 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 2025 financial year, show NOK 4.3m in revenue and NOK 132,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 132,000
Equity
NOK 57,000
Est. value
NOK 534,000

Financial health · 2025

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

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

Who owns DRØMMEBIL AS?

DEJAN JANIC
DRØMMEBIL AS
NOK 4.3m rev. · NOK 132,000 profit

DRØMMEBIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRØMMEBIL AS

Who owns DRØMMEBIL AS?

DEJAN JANIC is the largest registered owner, with 100.0%.

What is the revenue of DRØMMEBIL AS?

DRØMMEBIL AS had revenue of NOK 4.3m in 2025.

Who is the general manager of DRØMMEBIL AS?

Dejan Janic is registered as general manager of DRØMMEBIL AS.

Where is DRØMMEBIL AS based?

DRØMMEBIL AS has its business address in Gardermoen.

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.