BIZTRAC BETA
COMPANY REGISTER PROFILE
976931920 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

BERGE SAG PROSJEKT AS

Org. no. 976931920 Limited company (AS) Vindafjord Incorporated 1996 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 5.4m
Incorporated 1996
Share capital NOK 3.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

BERGE SAG PROSJEKT AS is registered as a limited company in Vindafjord, Rogaland with organisation number 976931920. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1996. Registered share capital is NOK 3.1m, divided into 3100 shares. The company's stated purpose is: “Selskapets formål er å drive kjøp/salg, herunder opparbeidelse av tomtearealer, utvikle og oppføre byggeprosjekter i egen regi og for andre, samt hva her står i forbindelse, herunder å delta i andre selskaper som driver tilsvarende virksomhet.”.

Former names: BJELLAND TOMTESELSKAP AS

Key figures · 2025

Operating profit
NOK −19,000
▼ −11 %
Equity
NOK 5.4m
▲ +0 %
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns BERGE SAG PROSJEKT AS?

BERGE SAG PROSJEKT AS
· NOK −19,000 profit

BERGE SAG PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGE SAG PROSJEKT AS

Who owns BERGE SAG PROSJEKT AS?

BERGE SAG GRUPPEN AS is the largest registered owner, with 100.0%.

Who is the general manager of BERGE SAG PROSJEKT AS?

Per Olaf Berge is registered as general manager of BERGE SAG PROSJEKT AS.

Where is BERGE SAG PROSJEKT AS based?

BERGE SAG PROSJEKT AS has its business address in Ølensvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.