BIZTRAC BETA
Construction of residential and non-residential buildings

HANDYMAN RENOVASJON AS

Org. no. 931924796 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 697,000
Operating profit NOK 71,000
Equity NOK 102,000
Incorporated 2023
Employees 8
Share capital NOK 60,000

HANDYMAN RENOVASJON AS is registered as a limited company in Lørenskog, Akershus with organisation number 931924796. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Renovering, oppussing av bolig, håndverkertjenester og vedlikehold.”. The most recent filed accounts, for the 2025 financial year, show NOK 697,000 in revenue and NOK 71,000 in operating profit.

Key figures · 2025

Revenue
NOK 697,000
Operating profit
NOK 71,000
Equity
NOK 102,000
Est. value
NOK 282,000

Financial health · 2025

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

Who owns HANDYMAN RENOVASJON AS?

BAO CHAU
HANDYMAN RENOVASJON AS
NOK 697,000 rev. · NOK 71,000 profit

HANDYMAN RENOVASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HANDYMAN RENOVASJON AS

Who owns HANDYMAN RENOVASJON AS?

BAO CHAU is the largest registered owner, with 100.0%.

What is the revenue of HANDYMAN RENOVASJON AS?

HANDYMAN RENOVASJON AS had revenue of NOK 697,000 in 2025.

Who is the general manager of HANDYMAN RENOVASJON AS?

Bao Chau is registered as general manager of HANDYMAN RENOVASJON AS.

Where is HANDYMAN RENOVASJON AS based?

HANDYMAN RENOVASJON AS has its business address in Fjellhamar.

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.