biztrac. BETA
COMPANY REGISTER PROFILE
923174028 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Masonry and bricklaying activities

BERGEN FLIS & MUR SPESIALISTEN AS

Org. no. 923174028 Limited company (AS) Øygarden Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 269,000
Equity NOK 553,000
Incorporated 2019
Share capital NOK 30,000

BERGEN FLIS & MUR SPESIALISTEN AS is registered as a limited company in Øygarden, Vestland with organisation number 923174028. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av flis og mur tjenester og varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 269,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +27 %
Operating profit
NOK 269,000
▲ +496 %
Equity
NOK 553,000
▲ +57 %
Est. value
NOK 971,000

Financial health · 2025

Liquidity
1.94
Good
Current assets ÷ current liabilities
Profitability
31.6%
Very good
Return on total assets
Solidity
65.1%
Very good
Equity as a share of total capital

Who owns BERGEN FLIS & MUR SPESIALISTEN AS?

BERGEN FLIS & MUR SPESIALISTEN AS
NOK 2.4m rev. · NOK 269,000 profit

BERGEN FLIS & MUR SPESIALISTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN FLIS & MUR SPESIALISTEN AS

Who owns BERGEN FLIS & MUR SPESIALISTEN AS?

Krzysztof Mikanik is the largest registered owner, with 100.0%.

What is the revenue of BERGEN FLIS & MUR SPESIALISTEN AS?

BERGEN FLIS & MUR SPESIALISTEN AS had revenue of NOK 2.4m in 2025.

Where is BERGEN FLIS & MUR SPESIALISTEN AS based?

BERGEN FLIS & MUR SPESIALISTEN AS has its business address in Misje.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.