BIZTRAC BETA
Masonry and bricklaying activities

JÆRMUR AS

Org. no. 989138502 Limited company (AS) Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 26.9m
Operating profit NOK 4.1m
Equity NOK 7.1m
Incorporated 2005
Employees 20
Share capital NOK 100,000

JÆRMUR AS is registered as a limited company in Hå, Rogaland with organisation number 989138502. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2005 and has 20 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å drive murer, bygge- og anleggsvirksomhet inkludert handel med bygningsvarer, samt deltakelse i andre selskaper det er naturlig å samarbeide med.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.9m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 26.9m
Operating profit
NOK 4.1m
Equity
NOK 7.1m
Est. value
NOK 15.9m

Financial health · 2025

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

Who owns JÆRMUR AS?

JÆRMUR HOLDING AS
JÆRMUR AS
NOK 26.9m rev. · NOK 4.1m profit

JÆRMUR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JÆRMUR AS own?

JÆRMUR AS holds a stake in 1 company:

See the full ownership structure →

Group structure

JÆRMUR AS er morselskap for 1 datterselskap:

Frequently asked questions about JÆRMUR AS

Who owns JÆRMUR AS?

JÆRMUR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JÆRMUR AS?

JÆRMUR AS had revenue of NOK 26.9m in 2024.

Who is the general manager of JÆRMUR AS?

Tore Dubland is registered as general manager of JÆRMUR AS.

Where is JÆRMUR AS based?

JÆRMUR AS has its business address in Varhaug.

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.