BIZTRAC BETA
Construction of residential and non-residential buildings

HUSBYGGARN AS

Org. no. 828598562 Limited company (AS) Ørland Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 10.3m
Operating profit NOK 1,000
Equity NOK 325,000
Incorporated 2022
Employees 8
Share capital NOK 500,000

HUSBYGGARN AS is registered as a limited company in Ørland, Trøndelag with organisation number 828598562. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Oppføring og renovering av bygninger og det som faller naturlig under byggevirksomhet. Selskapet kan også engasjere seg ved kjøp og salg av aksjer og verdipapirer, samt andre tiltak beslektet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.3m in revenue and NOK 1,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.3m
Operating profit
NOK 1,000
Equity
NOK 325,000
Est. value
NOK 143,000

Financial health · 2024

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

Who owns HUSBYGGARN AS?

HUSBYGGARN HOLDING AS
HUSBYGGARN AS
NOK 10.3m rev. · NOK 1,000 profit

HUSBYGGARN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSBYGGARN AS

Who owns HUSBYGGARN AS?

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

What is the revenue of HUSBYGGARN AS?

HUSBYGGARN AS had revenue of NOK 10.3m in 2024.

Who is the general manager of HUSBYGGARN AS?

Ole Jakob Hammertrø is registered as general manager of HUSBYGGARN AS.

Where is HUSBYGGARN AS based?

HUSBYGGARN AS has its business address in Bjugn.

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.