BIZTRAC BETA
Masonry and bricklaying activities

B. GULLAKSEN MUR & FLIS AS

Org. no. 930943711 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 12,000
Equity NOK 32,000
Incorporated 2023
Share capital NOK 30,000

B. GULLAKSEN MUR & FLIS AS is registered as a limited company in Bergen, Vestland with organisation number 930943711. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Mur- og byggtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 12,000
Equity
NOK 32,000
Est. value
NOK 50,000

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns B. GULLAKSEN MUR & FLIS AS?

BJARNE JOHAN SÆLE GULLAKSEN
B. GULLAKSEN MUR & FLIS AS
NOK 3.0m rev. · NOK 12,000 profit

B. GULLAKSEN MUR & FLIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about B. GULLAKSEN MUR & FLIS AS

Who owns B. GULLAKSEN MUR & FLIS AS?

BJARNE JOHAN SÆLE GULLAKSEN is the largest registered owner, with 100.0%.

What is the revenue of B. GULLAKSEN MUR & FLIS AS?

B. GULLAKSEN MUR & FLIS AS had revenue of NOK 3.0m in 2025.

Who is the general manager of B. GULLAKSEN MUR & FLIS AS?

Bjarne Johan Sæle Gullaksen is registered as general manager of B. GULLAKSEN MUR & FLIS AS.

Where is B. GULLAKSEN MUR & FLIS AS based?

B. GULLAKSEN MUR & FLIS AS has its business address in Bergen.

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.