BIZTRAC BETA
Development of building projects

TST RENOVERING AS

Org. no. 916464843 Limited company (AS) Lillestrøm Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 369,000
Operating profit NOK −34,000
Equity NOK 121,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−34k kr).

TST RENOVERING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 916464843. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp, salg, renovering, fornying av bolig, eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 369,000 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 369,000
Operating profit
NOK −34,000
Equity
NOK 121,000
Est. value
NOK 111,000

Financial health · 2024

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns TST RENOVERING AS?

TOM SJUE TARHEIM
TST RENOVERING AS
NOK 369,000 rev. · NOK −34,000 profit

TST RENOVERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TST RENOVERING AS

Who owns TST RENOVERING AS?

TOM SJUE TARHEIM is the largest registered owner, with 100.0%.

What is the revenue of TST RENOVERING AS?

TST RENOVERING AS had revenue of NOK 369,000 in 2024.

Who is the general manager of TST RENOVERING AS?

Tom Sjue Tarheim is registered as general manager of TST RENOVERING AS.

Where is TST RENOVERING AS based?

TST RENOVERING AS has its business address in Skedsmokorset.

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.