BIZTRAC BETA
Civil engineering activities

FIDJELAND UTBYGGING AS

Org. no. 980733661 Limited company (AS) Sandnes Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK −330,000
Equity NOK 5.7m
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−330k kr).

FIDJELAND UTBYGGING AS is registered as a limited company in Sandnes, Rogaland with organisation number 980733661. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Prosjektering og utbygging av bolig og hytteområder og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK −330,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK −330,000
Equity
NOK 5.7m
Est. value
NOK 11.0m

Financial health · 2024

Liquidity
2.05
Very 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 FIDJELAND UTBYGGING AS?

BERLAND BETONG AS
FIDJELAND UTBYGGING AS
NOK 7.9m rev. · NOK −330,000 profit

FIDJELAND UTBYGGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIDJELAND UTBYGGING AS

Who owns FIDJELAND UTBYGGING AS?

BERLAND BETONG AS is the largest registered owner, with 100.0%.

What is the revenue of FIDJELAND UTBYGGING AS?

FIDJELAND UTBYGGING AS had revenue of NOK 7.9m in 2024.

Who is the general manager of FIDJELAND UTBYGGING AS?

Leif Berland is registered as general manager of FIDJELAND UTBYGGING AS.

Where is FIDJELAND UTBYGGING AS based?

FIDJELAND UTBYGGING AS has its business address in Sandnes.

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.