BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER GB HASLUM AS

Org. no. 912376370 Limited company (AS) Kragerø Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 26.1m
Operating profit NOK 4.3m
Equity NOK 308,000
Incorporated 2013
Employees 6
Share capital NOK 30,000

BYGGMESTER GB HASLUM AS is registered as a limited company in Kragerø, Telemark with organisation number 912376370. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets hovedformål er ordinær entreprenør virksomhet innen bygg og anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.1m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 26.1m
Operating profit
NOK 4.3m
Equity
NOK 308,000
Est. value
NOK 11.9m

Financial health · 2024

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

Who owns BYGGMESTER GB HASLUM AS?

GB HASLUM AS
BYGGMESTER GB HASLUM AS
NOK 26.1m rev. · NOK 4.3m profit

BYGGMESTER GB HASLUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGMESTER GB HASLUM AS

Who owns BYGGMESTER GB HASLUM AS?

GB HASLUM AS is the largest registered owner, with 90.0%.

What is the revenue of BYGGMESTER GB HASLUM AS?

BYGGMESTER GB HASLUM AS had revenue of NOK 26.1m in 2024.

Who is the general manager of BYGGMESTER GB HASLUM AS?

Glenn Haslum is registered as general manager of BYGGMESTER GB HASLUM AS.

Where is BYGGMESTER GB HASLUM AS based?

BYGGMESTER GB HASLUM AS has its business address in Stabbestad.

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.