BIZTRAC BETA
Intermediation service activities for personal services

VASKEHJELP AS

Org. no. 917158142 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 28.2m
Operating profit NOK −4.4m
Equity NOK 2.8m
Incorporated 2016
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,4 mill kr).

VASKEHJELP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917158142. The business is classified under intermediation service activities for personal services (NACE 96.400). The company was incorporated in 2016. Registered share capital is NOK 600,000, divided into 500 shares. The company's stated purpose is: “Formidle kontakt mellom oppdragsgivere og oppdragstakere innen renhold og rydding og andre beslektede gjøremål. Innunder formålet faller også å drive renhold og rydding i egen regi samt deltakelse i andre selskaper med tilsvarende eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.2m in revenue and NOK −4.4m in operating profit.

Key figures · 2024

Revenue
NOK 28.2m
Operating profit
NOK −4.4m
Equity
NOK 2.8m
Est. value
NOK 20.6m

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.4%
Good
Equity as a share of total capital

Who owns VASKEHJELP AS?

DIGITAL MARKEDSPLASS AS
VASKEHJELP AS
NOK 28.2m rev. · NOK −4.4m profit

VASKEHJELP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VASKEHJELP AS

Who owns VASKEHJELP AS?

DIGITAL MARKEDSPLASS AS is the largest registered owner, with 100.0%.

What is the revenue of VASKEHJELP AS?

VASKEHJELP AS had revenue of NOK 28.2m in 2024.

Where is VASKEHJELP AS based?

VASKEHJELP AS has its business address in Trondheim.

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.