BIZTRAC BETA
Masonry and bricklaying activities

MUR & FLIS AS

Org. no. 975363201 Limited company (AS) Tromsø Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 9.2m
Operating profit NOK 369,000
Equity NOK 2.0m
Incorporated 1995
Employees 7
Share capital NOK 30,000

MUR & FLIS AS is registered as a limited company in Tromsø, Troms with organisation number 975363201. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1995 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 285 shares. The company's stated purpose is: “Håndverkvirksomhet og handel og hva hermed står i forbindelse, herunder å delta i andre selskaper med forretningsmessig formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.2m in revenue and NOK 369,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.2m
Operating profit
NOK 369,000
Equity
NOK 2.0m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns MUR & FLIS AS?

TOR BJØRNAR HANSEN
MUR & FLIS AS
NOK 9.2m rev. · NOK 369,000 profit

MUR & FLIS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MUR & FLIS AS own?

MUR & FLIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUR & FLIS AS

Who owns MUR & FLIS AS?

TOR BJØRNAR HANSEN is the largest registered owner, with 33.3%.

What is the revenue of MUR & FLIS AS?

MUR & FLIS AS had revenue of NOK 9.2m in 2025.

Who is the general manager of MUR & FLIS AS?

Frode Bjarne Olsen is registered as general manager of MUR & FLIS AS.

Where is MUR & FLIS AS based?

MUR & FLIS AS has its business address in Tromsø.

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.