BIZTRAC BETA
Masonry and bricklaying activities

BRØDRENE MEDALEN AS

Org. no. 997103092 Limited company (AS) Gjesdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 87.9m
Operating profit NOK 9.3m
Equity NOK 22.7m
Incorporated 2011
Employees 21
Share capital NOK 100,000

BRØDRENE MEDALEN AS is registered as a limited company in Gjesdal, Rogaland with organisation number 997103092. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2011 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av murertjenester for rehabilitering, nybygg og ombygging. Erverve tomter, bygg og eiendommer for uvikling, drift eller salg og hva som her må stå i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 87.9m in revenue and NOK 9.3m in operating profit.

Key figures · 2024

Revenue
NOK 87.9m
Operating profit
NOK 9.3m
Equity
NOK 22.7m
Est. value
NOK 38.7m

Financial health · 2024

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

Who owns BRØDRENE MEDALEN AS?

FRANK MEDALEN
BRØDRENE MEDALEN AS
NOK 87.9m rev. · NOK 9.3m profit

BRØDRENE MEDALEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRØDRENE MEDALEN AS own?

BRØDRENE MEDALEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BRØDRENE MEDALEN AS

Who owns BRØDRENE MEDALEN AS?

FRANK MEDALEN is the largest registered owner, with 50.0%.

What is the revenue of BRØDRENE MEDALEN AS?

BRØDRENE MEDALEN AS had revenue of NOK 87.9m in 2024.

Where is BRØDRENE MEDALEN AS based?

BRØDRENE MEDALEN AS has its business address in Ålgård.

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.