BIZTRAC BETA
Other specialised construction activities in construction of buildings

INNLANDET FLIS & MUR AS

Org. no. 925794813 Limited company (AS) Gjøvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 318,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 300,000

INNLANDET FLIS & MUR AS is registered as a limited company in Gjøvik, Innlandet with organisation number 925794813. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2020. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Å utføre mur- og flisarbeider samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 318,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 318,000
Equity
NOK 1.1m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.1%
Good
Equity as a share of total capital

Who owns INNLANDET FLIS & MUR AS?

NORDBOHUS INNLANDET AS
INNLANDET FLIS & MUR AS
NOK 7.6m rev. · NOK 318,000 profit

INNLANDET FLIS & MUR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INNLANDET FLIS & MUR AS

Who owns INNLANDET FLIS & MUR AS?

NORDBOHUS INNLANDET AS is the largest registered owner, with 50.0%.

What is the revenue of INNLANDET FLIS & MUR AS?

INNLANDET FLIS & MUR AS had revenue of NOK 7.6m in 2024.

Who is the general manager of INNLANDET FLIS & MUR AS?

Bård Are Fruseth is registered as general manager of INNLANDET FLIS & MUR AS.

Where is INNLANDET FLIS & MUR AS based?

INNLANDET FLIS & MUR 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.