biztrac. BETA
COMPANY REGISTER PROFILE
933923347 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

H.L BYGG & DESIGN AS

Org. no. 933923347 Limited company (AS) Fredrikstad Incorporated 2024 Active
Revenue 2025 NOK 3.3m
Operating profit NOK 121,000
Equity NOK 167,000
Incorporated 2024
Share capital NOK 30,000

H.L BYGG & DESIGN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933923347. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
▲ +965 %
Operating profit
NOK 121,000
▲ +88 %
Equity
NOK 167,000
▲ +108 %
Est. value
NOK 397,000

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
18.1%
Very good
Return on total assets
Solidity
15.5%
Satisfactory
Equity as a share of total capital

Who owns H.L BYGG & DESIGN AS?

H.L BYGG & DESIGN AS
NOK 3.3m rev. · NOK 121,000 profit

H.L BYGG & DESIGN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about H.L BYGG & DESIGN AS

Who owns H.L BYGG & DESIGN AS?

Jon Marius Hansen is the largest registered owner, with 50.0%.

What is the revenue of H.L BYGG & DESIGN AS?

H.L BYGG & DESIGN AS had revenue of NOK 3.3m in 2025.

Where is H.L BYGG & DESIGN AS based?

H.L BYGG & DESIGN AS has its business address in Torp.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.