BIZTRAC BETA
Manufacture of metal structures and parts of structures

TP-PRODUCTS AS

Org. no. 919207965 Limited company (AS) Drammen Incorporated 1968 Active
Ownership graph ↗
Revenue 2025 NOK 246.8m
Operating profit NOK 36.0m
Equity NOK 76.3m
Incorporated 1968
Employees 89
Share capital NOK 1.5m

Signals

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

TP-PRODUCTS AS is registered as a limited company in Drammen, Buskerud with organisation number 919207965. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 1968 and has 89 registered employees. Registered share capital is NOK 1.5m, divided into 1485060 shares. The company's stated purpose is: “Produksjon og omsetning.”. The most recent filed accounts, for the 2025 financial year, show NOK 246.8m in revenue and NOK 36.0m in operating profit.

Key figures · 2025

Revenue
NOK 246.8m
Operating profit
NOK 36.0m
Equity
NOK 76.3m
Est. value
NOK 162.9m

Financial health · 2025

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

Who owns TP-PRODUCTS AS?

TP BIDCO HOLDING AS
TP-PRODUCTS AS
NOK 246.8m rev. · NOK 36.0m profit

TP-PRODUCTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TP-PRODUCTS AS

Who owns TP-PRODUCTS AS?

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

What is the revenue of TP-PRODUCTS AS?

TP-PRODUCTS AS had revenue of NOK 246.8m in 2025.

Who is the general manager of TP-PRODUCTS AS?

Jan Inge Runningen is registered as general manager of TP-PRODUCTS AS.

Where is TP-PRODUCTS AS based?

TP-PRODUCTS AS has its business address in Drammen.

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.