Algemene Schrijn- En Timmerwerken Van Audenhove (SPRL)

Active
VAT

BE 0828.604.781

Address
Langestraat 22
9570 Lierde
Established
12-08-2010
Principal activity
Joinery works

Crisis resilience of Algemene Schrijn- En Timmerwerken Van Audenhove

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

Read more

Financial data of Algemene Schrijn- En Timmerwerken Van Audenhove

2022 Financial statements 2021 Financial statements 2020 Financial statements 2019
Profit/Loss €28,475
9%
€26,209
-23%
€34,089
176%
€12,356
Equity €28,674
> 1.000%
€200
102%
-€8,010
-74%
-€4,599
Gross margin €45,739
-9%
€50,090
-1%
€50,464
56%
€32,365

Frequently asked questions

What is the VAT number of Algemene Schrijn- En Timmerwerken Van Audenhove?
The VAT number of Algemene Schrijn- En Timmerwerken Van Audenhove is BE0828604781.
When was Algemene Schrijn- En Timmerwerken Van Audenhove founded?
Algemene Schrijn- En Timmerwerken Van Audenhove was founded on 12-08-2010.
What is the address of Algemene Schrijn- En Timmerwerken Van Audenhove?
The current registered office of Algemene Schrijn- En Timmerwerken Van Audenhove is located at Langestraat 22, 9570 Lierde.
When was the last time Algemene Schrijn- En Timmerwerken Van Audenhove filed their annual financial statements?
The most recent financial statements of Algemene Schrijn- En Timmerwerken Van Audenhove were filed on 30-08-2023. You can view them here.
How many employees does Algemene Schrijn- En Timmerwerken Van Audenhove have?
There are currently no employees working at Algemene Schrijn- En Timmerwerken Van Audenhove or no workforce information is available.
What is the annual turnover of Algemene Schrijn- En Timmerwerken Van Audenhove?
At the time of its most recent financial statements, Algemene Schrijn- En Timmerwerken Van Audenhove did not publish any turnover figures. Algemene Schrijn- En Timmerwerken Van Audenhove reported a gross margin of €45,739.17.
Address

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


More details