Familiehulp kinderopvang De Speelboom (ASBL)

Active
VAT

BE 0443.631.280

Address
Rue Royale 294
1210 Saint-Josse-Ten-Noode
Established
13-12-1989
Principal activity
Nurseries and day-care centres

Crisis resilience of Familiehulp kinderopvang De Speelboom

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

Read more

Financial data of Familiehulp kinderopvang De Speelboom

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Turnover €1,842,703
32%
€1,393,661
21%
€1,150,005
27%
€907,388
Profit/Loss €495,915
990%
€45,478
-88%
€391,209
102%
€193,317
Equity €6,287,022
19%
€5,292,409
50%
€3,529,455
9%
€3,225,456
Gross margin €8,185,381
32%
€6,200,541
11%
€5,605,326
8%
€5,197,743
Employees 135,6 FTE
16%
117 FTE
3%
113,4 FTE
6%
107,3 FTE

Frequently asked questions

What is the VAT number of Familiehulp kinderopvang De Speelboom?
The VAT number of Familiehulp kinderopvang De Speelboom is BE0443631280.
When was Familiehulp kinderopvang De Speelboom founded?
Familiehulp kinderopvang De Speelboom was founded on 13-12-1989.
What is the address of Familiehulp kinderopvang De Speelboom?
The current registered office of Familiehulp kinderopvang De Speelboom is located at Rue Royale 294, 1210 Saint-Josse-Ten-Noode.
When was the last time Familiehulp kinderopvang De Speelboom filed their annual financial statements?
The most recent financial statements of Familiehulp kinderopvang De Speelboom were filed on 09-07-2024. You can view them here.
How many employees does Familiehulp kinderopvang De Speelboom have?
There are 135,6 FTEs working at Familiehulp kinderopvang De Speelboom according to the staff figures in the most recent financial statements.
What is the annual turnover of Familiehulp kinderopvang De Speelboom?
At the time of its most recent financial statements, Familiehulp kinderopvang De Speelboom recorded a total turnover of €1,842,703.25.
Address

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


More details