BIZTRAC BETA
Other specialised construction activities n.e.c.

GJERDE BETONGSAGING AS

Org. no. 831391952 Limited company (AS) Strand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 628,000
Equity NOK 290,000
Incorporated 2023
Share capital NOK 100,000

GJERDE BETONGSAGING AS is registered as a limited company in Strand, Rogaland with organisation number 831391952. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, betongsaging, kjerneboring, samt hva som herved står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 628,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 628,000
Equity
NOK 290,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns GJERDE BETONGSAGING AS?

A. GJERDE HOLDING AS
GJERDE BETONGSAGING AS
NOK 4.1m rev. · NOK 628,000 profit

GJERDE BETONGSAGING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJERDE BETONGSAGING AS

Who owns GJERDE BETONGSAGING AS?

A. GJERDE HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of GJERDE BETONGSAGING AS?

GJERDE BETONGSAGING AS had revenue of NOK 4.1m in 2025.

Who is the general manager of GJERDE BETONGSAGING AS?

André Gjerde is registered as general manager of GJERDE BETONGSAGING AS.

Where is GJERDE BETONGSAGING AS based?

GJERDE BETONGSAGING AS has its business address in Tau.

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.