BIZTRAC BETA
Masonry and bricklaying activities

BRATLAND MUR OG FLIS AS

Org. no. 928701190 Limited company (AS) Nesbyen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −27,000
Equity NOK 282,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).

BRATLAND MUR OG FLIS AS is registered as a limited company in Nesbyen, Buskerud with organisation number 928701190. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levere murer- og flisleggertjenester samt kjøp og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −27,000
Equity
NOK 282,000
Est. value
NOK 810,000

Financial health · 2025

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

Who owns BRATLAND MUR OG FLIS AS?

CHRIS ERIC BRATLAND
BRATLAND MUR OG FLIS AS
NOK 2.0m rev. · NOK −27,000 profit

BRATLAND MUR OG FLIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRATLAND MUR OG FLIS AS

Who owns BRATLAND MUR OG FLIS AS?

CHRIS ERIC BRATLAND is the largest registered owner, with 100.0%.

What is the revenue of BRATLAND MUR OG FLIS AS?

BRATLAND MUR OG FLIS AS had revenue of NOK 2.0m in 2025.

Who is the general manager of BRATLAND MUR OG FLIS AS?

Chris Eric Bratland is registered as general manager of BRATLAND MUR OG FLIS AS.

Where is BRATLAND MUR OG FLIS AS based?

BRATLAND MUR OG FLIS AS has its business address in Nesbyen.

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.