BIZTRAC BETA
Joinery installation

TP TOTAL AS

Org. no. 913421817 Limited company (AS) Rollag Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −179,000
Equity NOK 769,000
Incorporated 2014
Share capital NOK 45,000

Signals

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

TP TOTAL AS is registered as a limited company in Rollag, Buskerud with organisation number 913421817. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2014. Registered share capital is NOK 45,000, divided into 1500 shares. The company's stated purpose is: “Drifte alle typer håndverkertjenester, delta og inneha eiendeler i andre selskaper med lignende virksomhet, kjøp og salg av varer og tjenester, konsulentvirksomhet og salg andre produkter og tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −179,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −179,000
Equity
NOK 769,000
Est. value
NOK 934,000

Financial health · 2025

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

Who owns TP TOTAL AS?

LEMOO HOLDING AS
TP TOTAL AS
NOK 1.7m rev. · NOK −179,000 profit

TP TOTAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TP TOTAL AS own?

TP TOTAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TP TOTAL AS

Who owns TP TOTAL AS?

LEMOO HOLDING AS is the largest registered owner, with 66.7%.

What is the revenue of TP TOTAL AS?

TP TOTAL AS had revenue of NOK 1.7m in 2025.

Where is TP TOTAL AS based?

TP TOTAL AS has its business address in Veggli.

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.