BIZTRAC BETA
Construction of residential and non-residential buildings

BOLIGSPESIALISTEN GLOMSAKER AS

Org. no. 930779628 Limited company (AS) Lindesnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 90,000
Equity NOK 563,000
Incorporated 2023
Share capital NOK 350,000

BOLIGSPESIALISTEN GLOMSAKER AS is registered as a limited company in Lindesnes, Agder with organisation number 930779628. 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 350,000, divided into 350 shares. The company's stated purpose is: “Oppføringer av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 90,000
Equity
NOK 563,000
Est. value
NOK 577,000

Financial health · 2025

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

Who owns BOLIGSPESIALISTEN GLOMSAKER AS?

A.G HOLDING AS
BOLIGSPESIALISTEN GLOMSAKER AS
NOK 4.6m rev. · NOK 90,000 profit

BOLIGSPESIALISTEN GLOMSAKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGSPESIALISTEN GLOMSAKER AS

Who owns BOLIGSPESIALISTEN GLOMSAKER AS?

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

What is the revenue of BOLIGSPESIALISTEN GLOMSAKER AS?

BOLIGSPESIALISTEN GLOMSAKER AS had revenue of NOK 4.6m in 2025.

Who is the general manager of BOLIGSPESIALISTEN GLOMSAKER AS?

Anders Glomsaker is registered as general manager of BOLIGSPESIALISTEN GLOMSAKER AS.

Where is BOLIGSPESIALISTEN GLOMSAKER AS based?

BOLIGSPESIALISTEN GLOMSAKER AS has its business address in Mandal.

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.