Google Finance is confused about ticker symbols

[Daren Black]

Ticker symbol AGQ is "ProShares Ultra Silver", Google Finance incorrectly identifies this as "ProShares UltraSh FTSE/Xinhua China 25".

Ticker symbol UVXY is "ProShares Ultra VIX Short-Term Fut ETF", Google Finance incorrectly identifies this as "ProShares Ultra Silver".

[Daren Black]

Still broken, although now Google Finance thinks AGQ = Arian Silver Corp (should be "ProShares Ultra Silver").

[FinanceFanatic]

Same issue here. I also used the link at the bottom of the GF page to report this (initially posted in the Google Search forum as well):

I tested with other ProShares symbols as well, some of them exhibit the incorrect description: 
SPXU - http://www.proshares.com/funds/spxu.html 
SBB - http://www.proshares.com/funds/sbb.html 

but some descriptions, e.g. the following, are correct: 
SH - http://www.proshares.com/funds/sh.html 
DOG - http://www.proshares.com/funds/dog.html 
PSQ - http://www.proshares.com/funds/psq.html

[FinanceFanatic]

Apparently someone just took some action, because now the NYSEARCA:AGQ = "ProShares Ultra Silver" is no longer available on Finance, even under a wrong name!

The ticker symbol now went back to defaulting to LON:AGQ, which is the Arian Silver Corp described by Darren below.

If I force Google Finance to show me "NYSEARCA:AGQ" by putting the full name into the search box, one eventually gets the correct market price, but now under a different wrong name: "ProShares UltraShort MSCI Japan (ETF)"

--

[Paul Parker]

Need both a market Identification code (eg three-letter exchange code)  AND  the specific company code, to identify correctly which exchange being traded AND the specific company. 

  

View:  http://www.wikinvest.com/wiki/List_of_Stock_Exchanges  

View:  http://www.iso15022.org/MIC/homepageMIC.htm

View:  http://en.wikipedia.org/wiki/International_Securities_Identification_Number 

[FinanceFanatic]

Well, dear Paul, if you need these codes why don't you go ahead and find them out yourself, since the provided information definitely allows you to do that!

In the meantime I also went ahead and added NYSEARCA:AGQ to my Google Finance portfolio which actually lead to some very surprising and unorthodox behavior. Please see the official ticker symbol website to obtain the relevant codes for this fund (there you can download the fact sheet for this or any other funds mentioned).

So the ticker symbol within my portfolio (and my personalized GF home page) CHANGES BY ITSELF! Even during a single trading session, the ticker I am following morphs to NYSEARCA:EWV or to NYSEARCA:UVXY without any action on my side!

Moreover, when I look at the diagram for the historical prices for NYSEARCA:AGQ, it actually jumps between the _different_ quotations of the different funds, such that one day it might give me the AGQ price, another day the EWV price though (all on the same graph)

That makes the information provided by Google Finance completely unreliable, distracting and even misleading. If this affected any of my investment decisions, I would actually not hesitate to sue Google, now that I uncovered this. Despite all your disclaimers you make yourself liable for knowingly displaying highly misleading information on your platform, along with other correct information. You are really risking Google's good name, reputation and legal responsibility by displaying such deceptive information over a long period of time, ignoring all notifications from this forum.

I will actually go ahead and consult with my lawyer about sending an official notice to Google on the issue.

[Richard Lejeune]

I am a stockholder in Petroamerica (PTAXF) which is a legitimate Canadian company.  It crashed (and recovered) yesterday and this seems to have related to a news story about a different scam company with a similar name:  Petro America (PTRZ).  The google news feed has all the PTAXF news stories mixed up with the PTRZ news stories.  How does one report this disaster so that they can correct it?

https://www.google.com/finance?cid=718034

[brady moritz]

This plagued me for a long time as well, but I think it's finally working again now. Just tested and it seems to load correctly (FINALLY, can't believe how long that was broken).