EQT MID MARKET US (NO.1) FEEDER LIMITED PARTNERSHIP

EQT MID MARKET US (NO.1) FEEDER LIMITED PARTNERSHIP is an Active company incorporated on 5 March 2015 (founded 10 years ago) with the registered office located in EDINBURGH.

Basic Information

Company #: SL019849

Incorporated: 5 March 2015 (10 years old)

Industry: None Supplied

Financial Information

Employees: N/A

Cash in Bank: N/A

Net Assets: N/A

Contact

Website: N/A

Email: N/A

Telephone: N/A

Address: 50 Lothian Road, Festival Square, Edinburgh, EH3 9WJ

Officers and Shareholders
Name Nationality Occupation Director
Eqt Mid Market Us (general Partner) Limited
Eqt Services (uk) Limited
Corporate Structure
Key Dates Timeline
All Accounts Compliance Corporation Tax Income Tax

Financial Year End 2016

5 March 2016

First Accounts Filing Deadline 2016

5 December 2016

Corporation Tax Payment Due 2016

6 December 2016

Company Tax Return Filing Deadline 2016

5 March 2017

Financial Year End 2017

5 March 2017

Annual Accounts Filing Deadline 2017

5 December 2017

Corporation Tax Payment Due 2017

6 December 2017

Company Tax Return Filing Deadline 2017

5 March 2018

Financial Year End 2018

5 March 2018

Annual Accounts Filing Deadline 2018

5 December 2018

Corporation Tax Payment Due 2018

6 December 2018

Company Tax Return Filing Deadline 2018

5 March 2019

Confirmation Statement Date 2024

4 March 2024

Confirmation Statement Date 2025

4 March 2025

Confirmation Statement Filing Deadline 2025

18 March 2025

Director Self Assessment Tax Year End 2025

5 April 2025

Director Self Assessment Tax Payment On Account

31 July 2025

Confirmation Statement Filing Deadline 2026

18 March 2026

Director Self Assessment Tax Year End 2026

5 April 2026

Director Self Assessment Tax Filing Deadline 2026

31 January 2027

This API endpoint allows you to retrieve detailed data for a single company using its company number. Below is an example API call:

curl -X GET "https://buddy.biz/api/v1/company/?api_key=YOUR_SECURE_API_KEY&company_number=SL019849"

For full documentation, please refer to our API Documentation.