BIZTRAC BETA
General cleaning of buildings

HEIKE VASK & VEDLIKEHOLD AS

Org. no. 998729408 Limited company (AS) Moss Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 253,000
Equity NOK 197,000
Incorporated 2012
Share capital NOK 30,000

HEIKE VASK & VEDLIKEHOLD AS is registered as a limited company in Moss, Østfold with organisation number 998729408. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renholdstjenester til bedrifter, off. instanser og privatpersoner. Kjøp og salg av varer i forbindelse med levering av samme tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 253,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 253,000
Equity
NOK 197,000
Est. value
NOK 904,000

Financial health · 2024

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

Who owns HEIKE VASK & VEDLIKEHOLD AS?

HEIKE HOLDING AS
HEIKE VASK & VEDLIKEHOLD AS
NOK 1.3m rev. · NOK 253,000 profit

HEIKE VASK & VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEIKE VASK & VEDLIKEHOLD AS

Who owns HEIKE VASK & VEDLIKEHOLD AS?

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

What is the revenue of HEIKE VASK & VEDLIKEHOLD AS?

HEIKE VASK & VEDLIKEHOLD AS had revenue of NOK 1.3m in 2024.

Who is the general manager of HEIKE VASK & VEDLIKEHOLD AS?

Heike Marcus Rasim Mera is registered as general manager of HEIKE VASK & VEDLIKEHOLD AS.

Where is HEIKE VASK & VEDLIKEHOLD AS based?

HEIKE VASK & VEDLIKEHOLD AS has its business address in Moss.

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.