Garmin Illustrates a Ascending Triangle Breakout

This morning Garmin (GRMN) broke out of a ascending triangle pattern (see full Garmin stock chart), and I think this makes for a great educational illustration so you can see visually what one looks like.

I posted on the ascending triangle pattern before, but to refresh your memory here is what one looks like,

Ascending Triangle Pattern

You can see the triangle formed, and what you look for then is the stock to break to the upside on strong accumulation volume. This is a bullish pattern, and now look at this chart of Garmin today:

Garmin Ascending Triangle Breakout

Garmin setup its ascending triangle pattern throughout August, and now today (the yellow bar) broke out of it to the upside. This chart is as of 10:48 AM, but by the end of the day you should see today’s volume above yesterday to signal a strong accumulation day, and the stock may very well be higher.

Do you use ascending triangles as part of your overall stock strategy?

-- Posted by Blain Reinkensmeyer on September 4, 2007 at 11:13 am --

Discuss this post in the StockTradingToGo Forum or email us.

Subscribe To StockTradingToGo.com

Got the StockTradingToGo Newsletter?
  • Professional Stock Picks and Tricks
  • Weekly Blog Highlights
  • Free Subscription to EPIC Insights!

Related Posts From the Past:


Comments on "Garmin Illustrates a Ascending Triangle Breakout" are closed unless our forms appear below.
Comment by Aaron
2007-09-04 15:19:46

The volume on GRMN is very nice today. The overall market volume isn’t very strong, but GRMN is going to finish well above average volume. Garmin is a tremendous growth story with the company performing very well fundamentally, and the charts look nice as well.

 
Name (required)
E-mail (required - never shown publicly)
URI
Subscribe to comments via email

Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.