Warning: mysqli_query(): (HY000/1030): Got error 28 from storage engine in /home/weeklyhub/public_html/wp-includes/wp-db.php on line 1924
Were Analysts Bearish Tui AG (LON:TUI) This Week?

Were Analysts Bearish Tui AG (LON:TUI) This Week?

October 12, 2017 - By Marie Mckinney

 Were Analysts Bearish Tui AG (LON:TUI) This Week?

Tui AG (LON:TUI) Ratings Coverage

Among 13 analysts covering TUI AG (LON:TUI), 7 have Buy rating, 1 Sell and 5 Hold. Therefore 54% are positive. TUI AG had 87 analyst reports since July 27, 2015 according to SRatingsIntel. As per Tuesday, July 26, the company rating was maintained by Barclays Capital. As per Friday, June 9, the company rating was maintained by Barclays Capital. The firm has “Overweight” rating given on Tuesday, December 8 by Barclays Capital. The firm has “Buy” rating by Shore Capital given on Thursday, August 10. The stock of Tui AG (LON:TUI) has “Buy” rating given on Monday, August 17 by Deutsche Bank. Goldman Sachs maintained the shares of TUI in report on Tuesday, August 16 with “Neutral” rating. The stock has “Overweight” rating by Morgan Stanley on Friday, September 18. Barclays Capital maintained Tui AG (LON:TUI) on Thursday, March 30 with “Overweight” rating. The stock has “Buy” rating by Shore Capital on Wednesday, March 29. The stock of Tui AG (LON:TUI) earned “Buy” rating by Shore Capital on Thursday, August 11. Below is a list of Tui AG (LON:TUI) latest ratings and price target changes.

29/09/2017 Broker: JP Morgan Rating: Overweight Old Target: GBX 1345.00 New Target: GBX 1345.00 Maintain
28/09/2017 Broker: Shore Capital Rating: Buy Maintain
05/09/2017 Broker: Barclays Capital Rating: Overweight New Target: GBX 1480.00 Maintain
14/08/2017 Broker: Credit Suisse Rating: Neutral Old Target: GBX 1100.00 New Target: GBX 1300.00 Upgrade
10/08/2017 Broker: Berenberg Rating: Buy New Target: GBX 1300.00 Maintain
10/08/2017 Broker: Shore Capital Rating: Buy Maintain
04/08/2017 Broker: Deutsche Bank Rating: Buy Old Target: GBX 1350.00 New Target: GBX 1350.00 Maintain
17/07/2017 Broker: Barclays Capital Rating: Overweight Old Target: GBX 1270.00 New Target: GBX 1270.00 Maintain
12/07/2017 Broker: JP Morgan Rating: Overweight Old Target: GBX 1325.00 New Target: GBX 1325.00 Maintain
09/06/2017 Broker: Barclays Capital Rating: Overweight Old Target: GBX 1280.00 New Target: GBX 1280.00 Maintain

About 776,557 shares traded. Tui AG (LON:TUI) has 0.00% since October 12, 2016 and is . It has underperformed by 16.70% the S&P500.

TUI AG is a Germany-based integrated tourism group. The company has market cap of GBP. The Firm operates through the following divisions: Central Region, Western Region, Hotels and Resorts, Cruises and Other Tourism. It currently has negative earnings. The Central Region segment comprises the tour operators and airlines in Germany and tour operators in Austria, Poland and Switzerland.

More notable recent Tui AG (LON:TUI) news were published by: Nasdaq.com which released: “TUI AG Reiterates FY Underlying EBITA Guidance – Quick Facts” on September 28, 2017, also Reuters.com with their article: “‘We’ll be here another 40 years’, top tour operator TUI tells Greece” published on October 06, 2017, Reuters.com published: “TUI sheds its stake in Hapag-Lloyd to focus on tourism” on July 10, 2017. More interesting news about Tui AG (LON:TUI) were released by: Bloomberg.com and their article: “Europeans Won’t Let Terror Spoil Their Vacations, TUI Says” published on August 22, 2017 as well as Seekingalpha.com‘s news article titled: “KKR Will Acquire Travelopia From TUI AG For $404 Million Cash” with publication date: February 16, 2017.

Receive News & Ratings Via Email - Enter your email address below to receive a concise daily summary of the latest news and analysts' ratings with our FREE daily email newsletter.




Free Email Newsletter

Enter your email address below to get the latest news and analysts' ratings for your stocks with our free daily email newsletter:



Warning: mysqli_query(): (HY000/1030): Got error 28 from storage engine in /home/weeklyhub/public_html/wp-includes/wp-db.php on line 1924