BIZTRAC BETA
Site preparation

T BERG ANLEGGSTEKNIKK AS

Org. no. 987046295 Limited company (AS) Holmestrand Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 33.6m
Operating profit NOK 862,000
Equity NOK 4.5m
Incorporated 2004
Employees 13
Share capital NOK 100,000

T BERG ANLEGGSTEKNIKK AS is registered as a limited company in Holmestrand, Vestfold with organisation number 987046295. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2004 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenør, prosjektering av grunnarbeider og VA-tekninske anlegg, betongarbeider, salg av anleggsrelaterte deler og masser.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.6m in revenue and NOK 862,000 in operating profit.

Key figures · 2025

Revenue
NOK 33.6m
Operating profit
NOK 862,000
Equity
NOK 4.5m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns T BERG ANLEGGSTEKNIKK AS?

T. BERG EIENDOM AS
T BERG ANLEGGSTEKNIKK AS
NOK 33.6m rev. · NOK 862,000 profit

T BERG ANLEGGSTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about T BERG ANLEGGSTEKNIKK AS

Who owns T BERG ANLEGGSTEKNIKK AS?

T. BERG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of T BERG ANLEGGSTEKNIKK AS?

T BERG ANLEGGSTEKNIKK AS had revenue of NOK 33.6m in 2025.

Who is the general manager of T BERG ANLEGGSTEKNIKK AS?

Thomas Berg is registered as general manager of T BERG ANLEGGSTEKNIKK AS.

Where is T BERG ANLEGGSTEKNIKK AS based?

T BERG ANLEGGSTEKNIKK AS has its business address in Holmestrand.

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.