Culinaire Slagerij Kristof En Isabel (SRL)

Active
VAT

BE 0865.682.042

Address
Rijksweg 330
8710 Wielsbeke
Established
09-06-2004
Principal activity
Retail trade of meat and meat products in specialised stores, except game and poultry meat

Crisis resilience of Culinaire Slagerij Kristof En Isabel

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

Read more

Financial data of Culinaire Slagerij Kristof En Isabel

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Profit/Loss €29,239
-73%
€108,815
629%
€14,937
-68%
€47,053
Equity €496,790
6%
€467,551
30%
€358,736
4%
€343,799
Gross margin €449,011
-25%
€600,015
18%
€506,862
13%
€447,138
Employees 8,1 FTE
-21%
10,3 FTE
-50%
20,8 FTE
93%
10,8 FTE

Frequently asked questions

What is the VAT number of Culinaire Slagerij Kristof En Isabel?
The VAT number of Culinaire Slagerij Kristof En Isabel is BE0865682042.
When was Culinaire Slagerij Kristof En Isabel founded?
Culinaire Slagerij Kristof En Isabel was founded on 09-06-2004.
What is the address of Culinaire Slagerij Kristof En Isabel?
The current registered office of Culinaire Slagerij Kristof En Isabel is located at Rijksweg 330, 8710 Wielsbeke.
When was the last time Culinaire Slagerij Kristof En Isabel filed their annual financial statements?
The most recent financial statements of Culinaire Slagerij Kristof En Isabel were filed on 03-10-2023. You can view them here.
How many employees does Culinaire Slagerij Kristof En Isabel have?
There are 8,1 FTEs working at Culinaire Slagerij Kristof En Isabel according to the staff figures in the most recent financial statements.
What is the annual turnover of Culinaire Slagerij Kristof En Isabel?
At the time of its most recent financial statements, Culinaire Slagerij Kristof En Isabel did not publish any turnover figures. Culinaire Slagerij Kristof En Isabel reported a gross margin of €449,010.88.
Address

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


More details