LIMTEC (ASBL)

Active
VAT

BE 0862.320.201

Full name
Limburgs Technologiecentrum Van De Metaalsector
Address
Wetenschapspark 35
3590 Diepenbeek
Established
01-01-2004
Principal activity
Other forms of education

Crisis resilience of LIMTEC

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

Read more

Financial data of LIMTEC

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Profit/Loss €2,637
156%
-€4,675
12%
-€5,289
8%
-€5,761
Equity €1,860,568
0%
€1,857,931
0%
€1,862,605
0%
€1,867,894
Gross margin -€3,194
-19%
-€2,679
7%
-€2,872
13%
-€3,313

Frequently asked questions

What is the VAT number of Limburgs Technologiecentrum Van De Metaalsector?
The VAT number of Limburgs Technologiecentrum Van De Metaalsector is BE0862320201.
When was Limburgs Technologiecentrum Van De Metaalsector founded?
Limburgs Technologiecentrum Van De Metaalsector was founded on 01-01-2004.
What is the address of Limburgs Technologiecentrum Van De Metaalsector?
The current registered office of Limburgs Technologiecentrum Van De Metaalsector is located at Wetenschapspark 35, 3590 Diepenbeek.
When was the last time Limburgs Technologiecentrum Van De Metaalsector filed their annual financial statements?
The most recent financial statements of Limburgs Technologiecentrum Van De Metaalsector were filed on 19-07-2024. You can view them here.
How many employees does Limburgs Technologiecentrum Van De Metaalsector have?
There are 5 FTEs working at Limburgs Technologiecentrum Van De Metaalsector according to the staff figures in the most recent financial statements.
What is the annual turnover of Limburgs Technologiecentrum Van De Metaalsector?
At the time of its most recent financial statements, Limburgs Technologiecentrum Van De Metaalsector did not publish any turnover figures. Limburgs Technologiecentrum Van De Metaalsector reported a gross margin of -€3,194.06.
Address

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


More details