BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

GLOMMEN MJØSEN HOLDING AS

Org. no. 924914505 Limited company (AS) Elverum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −2.2m
Equity NOK 91.3m
Incorporated 2020
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

GLOMMEN MJØSEN HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 924914505. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2020. Registered share capital is NOK 1.1m, divided into 300 shares. The company's stated purpose is: “Eie og forvalte aksjer, investere og delta i andre selskaper samt annen virksomhet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −2.2m
Equity
NOK 91.3m
Est. value
NOK 49.3m

Financial health · 2024

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

Who owns GLOMMEN MJØSEN HOLDING AS?

GLOMMEN MJØSEN SKOG SA
GLOMMEN MJØSEN HOLDING AS
· NOK −2.2m profit

GLOMMEN MJØSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLOMMEN MJØSEN HOLDING AS own?

GLOMMEN MJØSEN HOLDING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about GLOMMEN MJØSEN HOLDING AS

Who owns GLOMMEN MJØSEN HOLDING AS?

GLOMMEN MJØSEN SKOG SA is the largest registered owner, with 100.0%.

Who is the general manager of GLOMMEN MJØSEN HOLDING AS?

Gunnar Aakrann Eek is registered as general manager of GLOMMEN MJØSEN HOLDING AS.

Where is GLOMMEN MJØSEN HOLDING AS based?

GLOMMEN MJØSEN HOLDING AS has its business address in Elverum.

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.