Algemene Bouwonderneming Gebr. Callens (SRL)

Active
VAT

BE 0457.604.527

Address
Willem Elsschotstraat 5
8870 Izegem
Established
03-04-1996
Principal activity
General construction of residential buildings

Crisis resilience of Algemene Bouwonderneming Gebr. Callens

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

Read more

Financial data of Algemene Bouwonderneming Gebr. Callens

2024 Financial statements 2023 Financial statements 2022 Financial statements 2021 Financial statements
Profit/Loss €40,089
29%
€31,157
-26%
€42,017
46%
€28,838
Equity €206,804
24%
€166,716
23%
€135,559
45%
€93,541
Gross margin €335,743
-4%
€350,263
7%
€326,358
15%
€284,392
Employees 3,1 FTE
-21%
3,9 FTE
3%
3,8 FTE
12%
3,4 FTE

Frequently asked questions

What is the VAT number of Algemene Bouwonderneming Gebr. Callens?
The VAT number of Algemene Bouwonderneming Gebr. Callens is BE0457604527.
When was Algemene Bouwonderneming Gebr. Callens founded?
Algemene Bouwonderneming Gebr. Callens was founded on 03-04-1996.
What is the address of Algemene Bouwonderneming Gebr. Callens?
The current registered office of Algemene Bouwonderneming Gebr. Callens is located at Willem Elsschotstraat 5, 8870 Izegem.
When was the last time Algemene Bouwonderneming Gebr. Callens filed their annual financial statements?
The most recent financial statements of Algemene Bouwonderneming Gebr. Callens were filed on 24-10-2024. You can view them here.
How many employees does Algemene Bouwonderneming Gebr. Callens have?
There are 3,1 FTEs working at Algemene Bouwonderneming Gebr. Callens according to the staff figures in the most recent financial statements.
What is the annual turnover of Algemene Bouwonderneming Gebr. Callens?
At the time of its most recent financial statements, Algemene Bouwonderneming Gebr. Callens did not publish any turnover figures. Algemene Bouwonderneming Gebr. Callens reported a gross margin of €335,742.84.
Address

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


More details