Marleen Vandewalle notarisvennootschap (SRL)

Active
VAT

BE 0815.844.135

Address
Wortegemplein (W.) 2
9790 Wortegem-Petegem
Established
25-06-2009
Principal activity
Activities of notaries

Crisis resilience of Marleen Vandewalle notarisvennootschap

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

Read more

Financial data of Marleen Vandewalle notarisvennootschap

2023 Financial statements 2022 Financial statements 2021 Financial statements 2020 Financial statements
Profit/Loss €29,742
-54%
€64,554
-16%
€76,541
-33%
€114,901
Equity €833,000
-9%
€918,500
-8%
€999,469
-1%
€1,012,927
Gross margin €355,873
-16%
€425,458
-7%
€459,855
6%
€433,912
Employees 2,3 FTE
-26%
3,1 FTE
-24%
4,1 FTE
21%
3,4 FTE

Frequently asked questions

What is the VAT number of Marleen Vandewalle notarisvennootschap?
The VAT number of Marleen Vandewalle notarisvennootschap is BE0815844135.
When was Marleen Vandewalle notarisvennootschap founded?
Marleen Vandewalle notarisvennootschap was founded on 25-06-2009.
What is the address of Marleen Vandewalle notarisvennootschap?
The current registered office of Marleen Vandewalle notarisvennootschap is located at Wortegemplein (W.) 2, 9790 Wortegem-Petegem.
When was the last time Marleen Vandewalle notarisvennootschap filed their annual financial statements?
The most recent financial statements of Marleen Vandewalle notarisvennootschap were filed on 16-07-2024. You can view them here.
How many employees does Marleen Vandewalle notarisvennootschap have?
There are 2,3 FTEs working at Marleen Vandewalle notarisvennootschap according to the staff figures in the most recent financial statements.
What is the annual turnover of Marleen Vandewalle notarisvennootschap?
At the time of its most recent financial statements, Marleen Vandewalle notarisvennootschap did not publish any turnover figures. Marleen Vandewalle notarisvennootschap reported a gross margin of €355,873.22.
Address

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


More details