BIZTRAC BETA
Masonry and bricklaying activities

MURMESTER ALF V. OLSEN AS

Org. no. 989193341 Limited company (AS) Gjøvik Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −34,000
Equity NOK 4.7m
Incorporated 2005
Share capital NOK 300,000

Signals

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

MURMESTER ALF V. OLSEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 989193341. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, deltagelse i andre selskaper samt annen virksomhet forbundet med dette. Selskapet kan eie fast eiendom. ”.

Key figures · 2024

Operating profit
NOK −34,000
Equity
NOK 4.7m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns MURMESTER ALF V. OLSEN AS?

ALF VEGARD HAUGLAND OLSEN
MURMESTER ALF V. OLSEN AS
· NOK −34,000 profit

MURMESTER ALF V. OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MURMESTER ALF V. OLSEN AS own?

MURMESTER ALF V. OLSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MURMESTER ALF V. OLSEN AS

Who owns MURMESTER ALF V. OLSEN AS?

ALF VEGARD HAUGLAND OLSEN is the largest registered owner, with 100.0%.

Who is the general manager of MURMESTER ALF V. OLSEN AS?

Alf Vegard Haugland Olsen is registered as general manager of MURMESTER ALF V. OLSEN AS.

Where is MURMESTER ALF V. OLSEN AS based?

MURMESTER ALF V. OLSEN AS has its business address in Gjøvik.

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.