BIZTRAC BETA
Site preparation

BJELLAND AS

Org. no. 984560443 Limited company (AS) Klepp Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 404.9m
Operating profit NOK 8.6m
Equity NOK 61.4m
Incorporated 2002
Employees 185
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BJELLAND AS is registered as a limited company in Klepp, Rogaland with organisation number 984560443. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2002 and has 185 registered employees. Registered share capital is NOK 2.0m, divided into 200 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg og hva herved har forbindelse, maskinutleie, kjøp, salg og utleie av fast eiendom, kjøp og salg aksjer samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 404.9m in revenue and NOK 8.6m in operating profit.

Key figures · 2024

Revenue
NOK 404.9m
Operating profit
NOK 8.6m
Equity
NOK 61.4m
Est. value
NOK 53.5m

Financial health · 2025

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

Who owns BJELLAND AS?

CE HOLDING AS
BJELLAND AS
NOK 404.9m rev. · NOK 8.6m profit

BJELLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJELLAND AS

Who owns BJELLAND AS?

CE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BJELLAND AS?

BJELLAND AS had revenue of NOK 404.9m in 2024.

Who is the general manager of BJELLAND AS?

Joakim Lund Hetland is registered as general manager of BJELLAND AS.

Where is BJELLAND AS based?

BJELLAND AS has its business address in Klepp Stasjon.

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.