BIZTRAC BETA
COMPANY REGISTER PROFILE
988336386 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Site preparation

TALGJE ANLEGG AS

Org. no. 988336386 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 754,000
Operating profit NOK 150,000
Equity NOK 795,000
Incorporated 2005
Share capital NOK 150,000

TALGJE ANLEGG AS is registered as a limited company in Stavanger, Rogaland with organisation number 988336386. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet heri sprengning av fjell og stein, graving og transport av jord, stein og grus. Muring med naturstein, legging av belegningstein samt asfaltering.”. The most recent filed accounts, for the 2025 financial year, show NOK 754,000 in revenue and NOK 150,000 in operating profit.

Key figures · 2025

Revenue
NOK 754,000
▼ −23 %
Operating profit
NOK 150,000
▼ −58 %
Equity
NOK 795,000
▲ +25 %
Est. value
NOK 972,000

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
11.9%
Good
Return on total assets
Solidity
69.8%
Very good
Equity as a share of total capital

Who owns TALGJE ANLEGG AS?

TALGJE ANLEGG AS
NOK 754,000 rev. · NOK 150,000 profit

TALGJE ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TALGJE ANLEGG AS

Who owns TALGJE ANLEGG AS?

TERJE ØSTEBØ is the largest registered owner, with 90.0%.

What is the revenue of TALGJE ANLEGG AS?

TALGJE ANLEGG AS had revenue of NOK 754,000 in 2025.

Who is the general manager of TALGJE ANLEGG AS?

Terje Østebø is registered as general manager of TALGJE ANLEGG AS.

Where is TALGJE ANLEGG AS based?

TALGJE ANLEGG AS has its business address in Talgje.

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.