Bitget App
Trade smarter
Buy cryptoMarketsTradeFuturesStocksEarnInstitutionAI & More
Tae Won Mulsan to cancel 319,442 shares, cutting outstanding stock to 7,280,558

Tae Won Mulsan to cancel 319,442 shares, cutting outstanding stock to 7,280,558

BitgetBitget2026/09/29 07:46
  • Tae Won Mulsan set the cancellation of 319,442 common shares from treasury stock, out of 7,600,000 shares outstanding.
  • Cancellation amount set at KRW 959.92 million, based on the Sept. 28, 2026 closing price.
  • Board resolution dated Sept. 29, 2026; cancellation scheduled for Jan. 29, 2027.
  • Post-cancellation common shares outstanding expected to fall to 7,280,558; par value per share is KRW 500.


Disclaimer: This news brief was created by Public Technologies (PUBT) using generative artificial intelligence. While PUBT strives to provide accurate and timely information, this AI-generated content is for informational purposes only and should not be interpreted as financial, investment, or legal advice. Tae Won Mulsan Co. Ltd. published the original content used to generate this news brief via DART, the regulatory disclosure system operated by the South Korea Financial Supervisory Service (FSS) (Ref. ID: 20260929800586), on September 29, 2026, and is solely responsible for the information contained therein.

0
0

Disclaimer: The content of this article solely reflects the author's opinion and does not represent the platform in any capacity. This article is not intended to serve as a reference for making investment decisions.

Understand the market, then trade.
Bitget offers one-stop trading for cryptocurrencies, stocks, and gold.
Trade now!

You may also like

Microsoft Global Service Outage Investigation: A Vulnerability Lurking for Four Months, Problem Identified Only After 15 Hours

A vulnerability in Microsoft systems was triggered last week during a routine traffic switching operation. After a sudden surge in traffic, servers experienced memory exhaustion. The automated disaster recovery system then transferred the traffic to other "healthy" servers, but this inadvertently brought the vulnerability into these systems as well, causing a chain reaction of failures. It took about 15 hours from the initial occurrence of sporadic malfunctions to Microsoft's confirmation of the widespread issue. Microsoft then took another 15 hours before starting to roll out a fix, resulting in downtime much longer than similar incidents.

华尔街见闻•2026/11/16 22:07
Microsoft Global Service Outage Investigation: A Vulnerability Lurking for Four Months, Problem Identified Only After 15 Hours