Lokaal Cultuurbeleid District Antwerpen (ASBL)

Active
VAT

BE 0463.979.803

Address
Columbiastraat 110
2030 Antwerpen
Established
25-05-1998
Principal activity
Management of cultural centres and multifunctional rooms with a cultural aspect

Crisis resilience of Lokaal Cultuurbeleid District Antwerpen

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

Read more

Financial data of Lokaal Cultuurbeleid District Antwerpen

2022 Financial statements 2021 Financial statements 2020 Financial statements 2019
Turnover -
-
€171,228
-
-
-
-
Profit/Loss -€79,524
-232%
€60,265
-65%
€171,316
614%
-€33,304
Equity €374,233
-18%
€453,757
15%
€393,492
77%
€222,176
Gross margin -€63,991
-185%
€75,249
-62%
€199,753
> 1.000%
-€8,025

Frequently asked questions

What is the VAT number of Lokaal Cultuurbeleid District Antwerpen?
The VAT number of Lokaal Cultuurbeleid District Antwerpen is BE0463979803.
When was Lokaal Cultuurbeleid District Antwerpen founded?
Lokaal Cultuurbeleid District Antwerpen was founded on 25-05-1998.
What is the address of Lokaal Cultuurbeleid District Antwerpen?
The current registered office of Lokaal Cultuurbeleid District Antwerpen is located at Columbiastraat 110, 2030 Antwerpen.
When was the last time Lokaal Cultuurbeleid District Antwerpen filed their annual financial statements?
The most recent financial statements of Lokaal Cultuurbeleid District Antwerpen were filed on 14-11-2023. You can view them here.
How many employees does Lokaal Cultuurbeleid District Antwerpen have?
There are currently no employees working at Lokaal Cultuurbeleid District Antwerpen or no workforce information is available.
What is the annual turnover of Lokaal Cultuurbeleid District Antwerpen?
At the time of its most recent financial statements, Lokaal Cultuurbeleid District Antwerpen did not publish any turnover figures. Lokaal Cultuurbeleid District Antwerpen reported a gross margin of -€63,990.86.
Address

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


More details