<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2005 (9) TMI 322 - HIGH COURT OF ANDHRA PRADESH</title>
    <link>https://www.taxtmi.com/caselaws?id=111021</link>
    <description>The court dismissed the application to condone the delay of 665 days in filing the application to set aside the ex parte order of winding up. The court found that the applicant failed to show sufficient cause for the delay and provide detailed reasons for the delay, emphasizing the need for expeditious action in contesting the order. The court also noted the applicant&#039;s awareness of the proceedings through previous involvement, ultimately leading to the dismissal of the application.</description>
    <language>en-us</language>
    <pubDate>Fri, 30 Sep 2005 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 19 Apr 2012 17:36:39 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=148037" rel="self" type="application/rss+xml"/>
    <item>
      <title>2005 (9) TMI 322 - HIGH COURT OF ANDHRA PRADESH</title>
      <link>https://www.taxtmi.com/caselaws?id=111021</link>
      <description>The court dismissed the application to condone the delay of 665 days in filing the application to set aside the ex parte order of winding up. The court found that the applicant failed to show sufficient cause for the delay and provide detailed reasons for the delay, emphasizing the need for expeditious action in contesting the order. The court also noted the applicant&#039;s awareness of the proceedings through previous involvement, ultimately leading to the dismissal of the application.</description>
      <category>Case-Laws</category>
      <law>Companies Law</law>
      <pubDate>Fri, 30 Sep 2005 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=111021</guid>
    </item>
  </channel>
</rss>