BIZTRAC BETA
Manufacture of bricks, tiles and construction products, in baked clay

JÆRBJELKEN NORGE AS

Org. no. 924529989 Limited company (AS) Time Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 18,000
Equity NOK 26,000
Incorporated 2020
Share capital NOK 30,000

JÆRBJELKEN NORGE AS is registered as a limited company in Time, Rogaland with organisation number 924529989. The business is classified under manufacture of bricks, tiles and construction products, in baked clay (NACE 23.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Produksjon av prefabrikerte mindre betong/teglprodukter, ellers generell støp og forskaling.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 18,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 18,000
Equity
NOK 26,000
Est. value
NOK 70,000

Financial health · 2024

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

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

Who owns JÆRBJELKEN NORGE AS?

MURMESTER HESKJE AS
JÆRBJELKEN NORGE AS
NOK 2.4m rev. · NOK 18,000 profit

JÆRBJELKEN NORGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JÆRBJELKEN NORGE AS

Who owns JÆRBJELKEN NORGE AS?

MURMESTER HESKJE AS is the largest registered owner, with 66.7%.

What is the revenue of JÆRBJELKEN NORGE AS?

JÆRBJELKEN NORGE AS had revenue of NOK 2.4m in 2024.

Who is the general manager of JÆRBJELKEN NORGE AS?

Arne Hystad is registered as general manager of JÆRBJELKEN NORGE AS.

Where is JÆRBJELKEN NORGE AS based?

JÆRBJELKEN NORGE AS has its business address in Bryne.

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.