BIZTRAC BETA
Construction of residential and non-residential buildings

HÅNDVERKSBYGG AS

Org. no. 938374473 Limited company (AS) Oslo Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 25.4m
Operating profit NOK 2.3m
Equity NOK 5.8m
Incorporated 1985
Employees 15
Share capital NOK 510,000

HÅNDVERKSBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 938374473. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1985 and has 15 registered employees. Registered share capital is NOK 510,000, divided into 150 shares. The company's stated purpose is: “Entreprenørvirksomhet og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 25.4m
Operating profit
NOK 2.3m
Equity
NOK 5.8m
Est. value
NOK 10.7m

Financial health · 2025

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

Who owns HÅNDVERKSBYGG AS?

STINE ASKAUTRUD
HÅNDVERKSBYGG AS
NOK 25.4m rev. · NOK 2.3m profit

HÅNDVERKSBYGG AS has 5 registered shareholders:

All shareholders and roles →

Which companies does HÅNDVERKSBYGG AS own?

HÅNDVERKSBYGG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HÅNDVERKSBYGG AS

Who owns HÅNDVERKSBYGG AS?

STINE ASKAUTRUD is the largest registered owner, with 42.7%.

What is the revenue of HÅNDVERKSBYGG AS?

HÅNDVERKSBYGG AS had revenue of NOK 25.4m in 2025.

Who is the general manager of HÅNDVERKSBYGG AS?

Stine Askautrud is registered as general manager of HÅNDVERKSBYGG AS.

Where is HÅNDVERKSBYGG AS based?

HÅNDVERKSBYGG AS has its business address in Oslo.

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.