Kriekels Algemene Schrijn- En Timmerwerken (SRL)

Active
VAT

BE 0840.775.808

Address
Helstraat 17
3721 Kortessem
Established
03-11-2011
Principal activity
Joinery works

Crisis resilience of Kriekels Algemene Schrijn- En Timmerwerken

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

Read more

Financial data of Kriekels Algemene Schrijn- En Timmerwerken

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Profit/Loss -€16,876
-530%
€3,927
129%
-€13,364
-283%
€7,293
Equity -€25,920
-187%
-€9,033
30%
-€12,961
< -1.000%
€404
Gross margin -€5,244
-131%
€17,049
108%
€8,203
-81%
€43,993
Employees -
-
-
-
0,5 FTE
-38%
0,8 FTE

Frequently asked questions

What is the VAT number of Kriekels Algemene Schrijn- En Timmerwerken?
The VAT number of Kriekels Algemene Schrijn- En Timmerwerken is BE0840775808.
When was Kriekels Algemene Schrijn- En Timmerwerken founded?
Kriekels Algemene Schrijn- En Timmerwerken was founded on 03-11-2011.
What is the address of Kriekels Algemene Schrijn- En Timmerwerken?
The current registered office of Kriekels Algemene Schrijn- En Timmerwerken is located at Helstraat 17, 3721 Kortessem.
When was the last time Kriekels Algemene Schrijn- En Timmerwerken filed their annual financial statements?
The most recent financial statements of Kriekels Algemene Schrijn- En Timmerwerken were filed on 01-02-2024. You can view them here.
How many employees does Kriekels Algemene Schrijn- En Timmerwerken have?
There are 1 FTEs working at Kriekels Algemene Schrijn- En Timmerwerken according to the staff figures in the most recent financial statements.
What is the annual turnover of Kriekels Algemene Schrijn- En Timmerwerken?
At the time of its most recent financial statements, Kriekels Algemene Schrijn- En Timmerwerken did not publish any turnover figures. Kriekels Algemene Schrijn- En Timmerwerken reported a gross margin of -€5,244.41.
Address

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


More details