BIZTRAC BETA
Masonry and bricklaying activities

MUR OG FLISSERVICE AS

Org. no. 982715067 Limited company (AS) Bergen Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 11.5m
Operating profit NOK 126,000
Equity NOK 1.9m
Incorporated 2000
Employees 15
Share capital NOK 400,000

MUR OG FLISSERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 982715067. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2000 and has 15 registered employees. Registered share capital is NOK 400,000, divided into 200 shares. The company's stated purpose is: “Håndtverksmessige tjenester med mur og flisarbeid, samt salg som knytter seg til dette. Deltakelse i andre virksomheter samt eie og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.5m in revenue and NOK 126,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.5m
Operating profit
NOK 126,000
Equity
NOK 1.9m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns MUR OG FLISSERVICE AS?

TAIM HOLDING AS
MUR OG FLISSERVICE AS
NOK 11.5m rev. · NOK 126,000 profit

MUR OG FLISSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MUR OG FLISSERVICE AS own?

MUR OG FLISSERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUR OG FLISSERVICE AS

Who owns MUR OG FLISSERVICE AS?

TAIM HOLDING AS is the largest registered owner, with 87.5%.

What is the revenue of MUR OG FLISSERVICE AS?

MUR OG FLISSERVICE AS had revenue of NOK 11.5m in 2024.

Where is MUR OG FLISSERVICE AS based?

MUR OG FLISSERVICE AS has its business address in Ytre Arna.

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.