biztrac. BETA
COMPANY REGISTER PROFILE
934311345 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

VASKEGATA AS

Org. no. 934311345 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK −101,000
Equity NOK −76,000
Incorporated 2024
Share capital NOK 510,000

Signals

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

VASKEGATA AS is registered as a limited company in Asker, Akershus with organisation number 934311345. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2024. Registered share capital is NOK 510,000, divided into 17000 shares. The company's stated purpose is: “Drift av vaskeanlegg, bilrelatert virksomhet, salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK −101,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
▲ +1489 %
Operating profit
NOK −101,000
▲ +79 %
Equity
NOK −76,000
▲ +83 %

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
-17.2%
Not satisfactory
Return on total assets
Solidity
-11.8%
Weak
Equity as a share of total capital

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

Who owns VASKEGATA AS?

VASKEGATA AS
NOK 3.9m rev. · NOK −101,000 profit

VASKEGATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VASKEGATA AS

Who owns VASKEGATA AS?

ELNA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VASKEGATA AS?

VASKEGATA AS had revenue of NOK 3.9m in 2025.

Where is VASKEGATA AS based?

VASKEGATA AS has its business address in Slemmestad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.