BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

GLOMSTAD AS

Org. no. 930873799 Limited company (AS) Aure Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 205,000
Operating profit NOK −18,000
Equity NOK 43,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

GLOMSTAD AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 930873799. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). 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 bygg, anlegg og transport - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 205,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 205,000
Operating profit
NOK −18,000
Equity
NOK 43,000
Est. value
NOK 87,000

Financial health · 2024

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

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

Who owns GLOMSTAD AS?

No shareholders are registered for GLOMSTAD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GLOMSTAD AS

What is the revenue of GLOMSTAD AS?

GLOMSTAD AS had revenue of NOK 205,000 in 2024.

Who is the general manager of GLOMSTAD AS?

Bjørn Egil Glomstad is registered as general manager of GLOMSTAD AS.

Where is GLOMSTAD AS based?

GLOMSTAD AS has its business address in Aure.

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.