BIZTRAC BETA
Other building and industrial cleaning activities

MB FASADEVASK AS

Org. no. 932681943 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −444,000
Equity NOK 945,000
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−444k kr).

MB FASADEVASK AS is registered as a limited company in Øygarden, Vestland with organisation number 932681943. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Vask av uteareal, vindusvask, vegger, tak og andre fasader for privathus, borettslag, sameier og for næringsbygg.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −444,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −444,000
Equity
NOK 945,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.1%
Very good
Equity as a share of total capital

Who owns MB FASADEVASK AS?

MARTIN BLOM AS
MB FASADEVASK AS
NOK 1.0m rev. · NOK −444,000 profit

MB FASADEVASK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MB FASADEVASK AS

Who owns MB FASADEVASK AS?

MARTIN BLOM AS is the largest registered owner, with 100.0%.

What is the revenue of MB FASADEVASK AS?

MB FASADEVASK AS had revenue of NOK 1.0m in 2024.

Who is the general manager of MB FASADEVASK AS?

Martin Arild Blom is registered as general manager of MB FASADEVASK AS.

Where is MB FASADEVASK AS based?

MB FASADEVASK AS has its business address in Rong.

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.