BIZTRAC BETA
Repair and maintenance of motor vehicles

BILDATA AS

Org. no. 926858289 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 423,000
Operating profit NOK −167,000
Equity NOK −92,000
Incorporated 2021
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−92k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−167k kr).

BILDATA AS is registered as a limited company in Lillestrøm, Akershus with organisation number 926858289. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Mekaniske og elektromekaniske reparasjoner av alle type kjøretøy”. The most recent filed accounts, for the 2025 financial year, show NOK 423,000 in revenue and NOK −167,000 in operating profit.

Key figures · 2025

Revenue
NOK 423,000
Operating profit
NOK −167,000
Equity
NOK −92,000

Financial health · 2025

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

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

Who owns BILDATA AS?

AURELIJA SIMANAVICIENE
BILDATA AS
NOK 423,000 rev. · NOK −167,000 profit

BILDATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILDATA AS

Who owns BILDATA AS?

AURELIJA SIMANAVICIENE is the largest registered owner, with 100.0%.

What is the revenue of BILDATA AS?

BILDATA AS had revenue of NOK 423,000 in 2025.

Who is the general manager of BILDATA AS?

Aurelija Simanaviciene is registered as general manager of BILDATA AS.

Where is BILDATA AS based?

BILDATA AS has its business address in Frogner.

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.