PEETERS T.P.I. (SA)

Active
VAT

BE 0872.257.355

Full name
Peeters Travaux Publics Et Industriels
Address
Chaussée de Ramet(IVR) 12
4400 Flémalle
Established
01-03-2005
Principal activity
Other building and industrial cleaning activities

Crisis resilience of PEETERS T.P.I.

Which companies are best armed against current economic trends and the energy crisis?

Read more

Financial data of PEETERS T.P.I.

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Turnover €10,277,523
0%
€10,226,440
8%
€9,471,451
24%
€7,616,021
Profit/Loss -€123,704
-427%
€37,838
-68%
€117,162
235%
-€87,094
Equity €3,888,458
-3%
€4,012,162
1%
€3,974,324
3%
€3,857,162
Gross margin €6,823,074
6%
€6,432,504
6%
€6,087,336
23%
€4,949,462
Employees 81 FTE
-2%
82,9 FTE
7%
77,8 FTE
5%
74,3 FTE

Frequently asked questions

What is the VAT number of Peeters Travaux Publics Et Industriels?
The VAT number of Peeters Travaux Publics Et Industriels is BE0872257355.
When was Peeters Travaux Publics Et Industriels founded?
Peeters Travaux Publics Et Industriels was founded on 01-03-2005.
What is the address of Peeters Travaux Publics Et Industriels?
The current registered office of Peeters Travaux Publics Et Industriels is located at Chaussée de Ramet(IVR) 12, 4400 Flémalle.
When was the last time Peeters Travaux Publics Et Industriels filed their annual financial statements?
The most recent financial statements of Peeters Travaux Publics Et Industriels were filed on 22-08-2024. You can view them here.
How many employees does Peeters Travaux Publics Et Industriels have?
There are 81 FTEs working at Peeters Travaux Publics Et Industriels according to the staff figures in the most recent financial statements.
What is the annual turnover of Peeters Travaux Publics Et Industriels?
At the time of its most recent financial statements, Peeters Travaux Publics Et Industriels recorded a total turnover of €10,277,523.00.
Address

  You have disabled Javascript on your computer. To use this website, please enable Javascript first.


More details