BIZTRAC BETA
Construction of residential and non-residential buildings

HUMLE BYGG AS

Org. no. 931407309 Limited company (AS) Askøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 69,000
Equity NOK 43,000
Incorporated 2023
Share capital NOK 30,000

HUMLE BYGG AS is registered as a limited company in Askøy, Vestland with organisation number 931407309. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen tømrer, byggetjenester 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.1m in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 69,000
Equity
NOK 43,000
Est. value
NOK 235,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HUMLE BYGG AS?

SVARTHUMLE HOLDING AS
HUMLE BYGG AS
NOK 3.1m rev. · NOK 69,000 profit

HUMLE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUMLE BYGG AS

Who owns HUMLE BYGG AS?

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

What is the revenue of HUMLE BYGG AS?

HUMLE BYGG AS had revenue of NOK 3.1m in 2025.

Who is the general manager of HUMLE BYGG AS?

Per Øyvind Svarthumle is registered as general manager of HUMLE BYGG AS.

Where is HUMLE BYGG AS based?

HUMLE BYGG AS has its business address in Hauglandshella.

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.