advertisement

Singer expected to start for the Royals against Indians

Kansas City Royals (67-82, fourth in the AL Central) vs. Cleveland Indians (73-74, second in the AL Central)

Cleveland; Monday, 4:10 p.m. EDT

PITCHING PROBABLES: Royals: Brady Singer (4-10, 0.00 ERA) Indians: Triston McKenzie (5-6, 4.28 ERA, 1.06 WHIP, 127 strikeouts)

BOTTOM LINE: Salvador Perez and the Royals will take on the Indians Monday.

The Indians are 36-36 on their home turf. Cleveland hitters have posted a team on-base percentage of .301 this season, led by Myles Straw with a mark of .348.

The Royals are 31-43 on the road. The Kansas City offense has compiled a .248 batting average as a team this season, Nicky Lopez leads the team with a mark of .300.

The Indians won the last meeting 4-2. Triston McKenzie notched his fourth victory and Owen Miller went 1-for-4 with a home run and three RBIs for Cleveland. Mike Minor took his 12th loss for Kansas City.

TOP PERFORMERS: Amed Rosario leads the Indians with 142 hits and has 51 RBIs.

Salvador Perez leads the Royals with 45 home runs and is slugging .542.

LAST 10 GAMES: Indians: 5-5, .225 batting average, 4.50 ERA, outscored opponents by one run

Royals: 5-5, .292 batting average, 5.04 ERA, outscored by four runs

INJURIES: Indians: Nick Sandlin: (shoulder), Shane Bieber: (shoulder), Harold Ramirez: (shoulder), Josh Naylor: (ankle), Wilson Ramos: (knee).

Royals: Brady Singer: (undisclosed), Mike Minor: (shoulder), Daniel Lynch: (calf), Richard Lovelady: (elbow), Brad Keller: (shoulder), Jakob Junis: (shoulder), Jesse Hahn: (shoulder), Wade Davis: (shoulder), Cam Gallagher: (knee).

___

The Associated Press created this story using technology provided by Data Skrive and data from Sportradar.

Article Comments
Guidelines: Keep it civil and on topic; no profanity, vulgarity, slurs or personal attacks. People who harass others or joke about tragedies will be blocked. If a comment violates these standards or our terms of service, click the "flag" link in the lower-right corner of the comment box. To find our more, read our FAQ.