BIZTRAC BETA
Business and other management consultancy activities

MJØSGLØTT HOLDING AS

Org. no. 958909365 Limited company (AS) Hamar Incorporated 1990 Active
Ownership graph ↗
Operating profit NOK −79,000
Equity NOK 6.5m
Incorporated 1990
Share capital NOK 165,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−79k kr).

MJØSGLØTT HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 958909365. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1990. Registered share capital is NOK 165,000, divided into 100 shares. The company's stated purpose is: “Investere i andre selskaper, herunder deltagelse i andre selskaper med lignende virksomhet og ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −79,000
Equity
NOK 6.5m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns MJØSGLØTT HOLDING AS?

BRITT KARINA GYLDENSKOG BERSTAD
MJØSGLØTT HOLDING AS
· NOK −79,000 profit

MJØSGLØTT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MJØSGLØTT HOLDING AS own?

MJØSGLØTT HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about MJØSGLØTT HOLDING AS

Who owns MJØSGLØTT HOLDING AS?

BRITT KARINA GYLDENSKOG BERSTAD is the largest registered owner, with 100.0%.

Who is the general manager of MJØSGLØTT HOLDING AS?

Britt Karina Gyldenskog Berstad is registered as general manager of MJØSGLØTT HOLDING AS.

Where is MJØSGLØTT HOLDING AS based?

MJØSGLØTT HOLDING AS has its business address in Hamar.

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.