Skip to main content

DUMB TRADERS ANONYMOUS

This morning on the television I saw AMEX ticker symbol CSN climb 800%, from $0.08 to $1.09. Wow, I though, that is a stock to investigate. What the heck is going on there? The last time I saw that jump, it was 2002 and I was buying SONUS Networks.

CSN is the symbol for City Networks, Inc. This is a Taiwanese based company that provides wireless access infrastructure and resells network hardware. They don't manufacture anything,and claim this in their company profile:

"The Company also created the Hotspot solution and the Next Generation Loops (NGL) solution, both of which help companies extend their business to the carrier's solution to meet people's communication inquires." (From E*Trade)

Their website, shows the last news update in December of 2004. So this is a company that hasn't done anything in the last 2 years except exist.

(Update: The stock is now at $0.24 with a 118% gain. Someone is getting smart).

So why did its stock go up so high? The news wire (Marketwatch) listed the ticker symbol for Brazil's Companhia Siderurgia Nacional as CSN. This company was listed on a news brief about Pfizer's recent layoffs as being a possible purchaser of Corus Group (CGA). Imagine your excitement finding a big biotech stock for $0.08 per share. Bargain hunters abound!!

The run-up of this stock is a clear indicator that automated electronic trading is a dangerous game. About 1.6 million shares of CSN were traded today, which is enormously more than the average daily volume of 90K that this stock sees. That probably means a bunch of traders out there made serious bank on this mixup, and a bunch more of the not so savvy home traders are about to buy a stinker stock that will lose 90% of its value in the next 7 days.

All of this likely because Marketwatch listed the wrong ticker symbol for a real company. The AMEX will likely cancel all of these trades in lieu of the mixup, if they ever realize that it happened.

Popular posts from this blog

Number of Primes

Anderson's Theorem (a) The number of primes in [1,n] is no more than 2+floor(n/2). The probability of n being prime when n is not prime is 1/2 - see Dasgupta,Papadimitriou,Vazirani "Algorithms" page 26. Therefore, the E(pi(n)) is n/2. (b) There does not exist another set of adjacent primes other than {1,2,3} 5: 2 + floor(5/2) = 2 + 2 = 4:=> {1,2,3,5} : 4 <= 4 7: 2 + floor(7/2) = 2 + 3 = 5 => {1,2,3,5,7} : 5 <= 5 11: 2 + floor(11/2) = 2 + 5 = 7 => {1,2,3,5,7,11} 6 <= 7 26: 2 + floor(26/2) = 15 => {1,2,3,5,7,11,13,17,19,23} : 10 <= 15 Lagrange's Theorem is Inaccurate Lagrange's theorem about primes states that pi(x) is the number of primes <= x. The pi(x) is approximately x/ln(x). He postulated that the lim of pi(x)/(x/lnx) as x-> infinity was 1. This is incorrect. if the number of primes is bounded by n/2 then refactoring and reducing Lagrange's Theorem results in the lim of ln(x) as x approaches infinity. This is alwa...

How To Cancel ATT Uverse

I was a subscriber to the AT&T Uverse service for a little over 2 years. In that time, we had experienced good service for the first year, and then it sucked. After 12 months, or there in, the service degraded quickly, and would stop working all together at times. At first it would die for a short period of time, usually when we were not home. Then it would get progressively worst, until there was an entire week of no service. We had technicians at the house trying to fix the service, but it would repeat the behavior quite consistently. On January 15th we finally gave up and switched to a lesser service, COX TV and Internet. In the past we had cable service and it was always reliable, but not as good as the AT&T digital service. COX doesn't have nearly as many HD channels, but that's not enough. We needed internet to be reliable, and AT&T couldn't deliver that. Cancelling the AT&T service was a nightmare. Try to find anything about such things on their web s...

DNS Custom Logs and selinux

If you google "named custom logs selinux" you will find quite a bit of chatter about setting up custom logs outside of /var/log for DNS (named). These posts are interesting, but they tend to be run on posts about learning selinux and becoming an expert on named. What you need to know? If you have setup custom logging locations in your /etc/named.conf file, such as:     channel default_file {         file "/var/log/named/default.log" versions 3 size 5m;         severity dynamic;         print-time yes;     }; Then you will likely see errors like this in /var/log/messages: Oct 26 11:41:13 namedsvr setroubleshoot: SELinux is preventing /usr/sbin/named from write access on the directory /var/named/chroot/var/log/named. For complete SELinux messages. run sealert -l 6eab4aaf-e615-4ade-9e88-4efdc789eaf2 Then you run the sealert command as suggested by the very friendly selinux audit log and yo...